diff --git a/9f0d77fa44e265a4e316f94be42554a5/description b/9f0d77fa44e265a4e316f94be42554a5/description
new file mode 100644
index 0000000..4e1687d
--- /dev/null
+++ b/9f0d77fa44e265a4e316f94be42554a5/description
@@ -0,0 +1,11 @@
+`ent list` should take a git-like --pretty=format:
+
+The immediate use is:
+* list all issues in state=inprogress, but only tell me the assignees of each
+
+I currently do this with a slow and awkward shell script:
+```
+for ISSUE_ID in $(ent list state=inprogress | grep '  ' | cut -f 1 -d ' '); do
+    ent show "${ISSUE_ID}" | grep -i assign
+done
+```
diff --git a/dd20d3ddc86ee802fe7b15e2c91dc160/comments/0efebcbcf60417a54382a408b99dadf5/description b/dd20d3ddc86ee802fe7b15e2c91dc160/comments/0efebcbcf60417a54382a408b99dadf5/description
new file mode 100644
index 0000000..74afbd6
--- /dev/null
+++ b/dd20d3ddc86ee802fe7b15e2c91dc160/comments/0efebcbcf60417a54382a408b99dadf5/description
@@ -0,0 +1,21 @@
+There's a fly in the ointment: we want to store tags as files in a
+directory, but file names are not allowed to contain the character `/`,
+and some of our current tags use `/` in the tag name.
+
+We could allow subdirectories of the `tags` directory, but it feels
+like that breaks the budding database abstraction of "a directory is a
+key/value store, filenames are the keys, file contents are the values".
+
+We could forbid `/` in tags and replace them with `.` or `_` or something,
+but that's a bit sad because i like `/` as the "hierarchy separator".
+
+Wikipedia claims, and experiment confirms:
+> The big solidus ⧸ (Unicode code point U+29F8) is permitted in Unix
+> and Windows filenames.
+
+<https://en.wikipedia.org/wiki/Filename#Problematic_characters>
+
+But that feels like madness.
+
+I think the least worst option is to replace `/` with `.` in tags.
+Opinions?