From 99f43accdc0ca24ece068c95cc6be20044c772fb Mon Sep 17 00:00:00 2001
From: Sebastian Kuzminsky <seb@highlab.com>
Date: Wed, 23 Jul 2025 17:58:06 -0600
Subject: [PATCH] add comment d05f01c7b06ef3354ee22dc614560fdd on issue
 dd20d3ddc86ee802fe7b15e2c91dc160

---
 .../d05f01c7b06ef3354ee22dc614560fdd/description | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 dd20d3ddc86ee802fe7b15e2c91dc160/comments/d05f01c7b06ef3354ee22dc614560fdd/description

diff --git a/dd20d3ddc86ee802fe7b15e2c91dc160/comments/d05f01c7b06ef3354ee22dc614560fdd/description b/dd20d3ddc86ee802fe7b15e2c91dc160/comments/d05f01c7b06ef3354ee22dc614560fdd/description
new file mode 100644
index 0000000..1fd3171
--- /dev/null
+++ b/dd20d3ddc86ee802fe7b15e2c91dc160/comments/d05f01c7b06ef3354ee22dc614560fdd/description
@@ -0,0 +1,16 @@
+Another option is to escape '/' in tags when turning them into filenames.
+
+Let's somewhat arbitrarily say we use ',' as the escape character.
+
+',' in a tag would be replaced with the two-character sequence ',0'
+in the filename.
+
+'/' in a tag would be replaced with ',1' in the filename.
+
+(And so on for any other characters we need to escape.)
+
+This would give the user the behavior we want, which is to be free to use
+'/' in tags.
+
+The implementation detail of escaped tags would be hidden from the user
+unless they dug into the on-disk format by hand.