update in response to comment

diff --git a/doc/design/external_special_remote_protocol.mdwn b/doc/design/external_special_remote_protocol.mdwn
index 365ee6cf4d0a87be16664855286d0ce69f4f0a12..3d2f0588aea6ec94568d9dd7e16a0917f20c6bd7 100644 (file)
--- a/doc/design/external_special_remote_protocol.mdwn
+++ b/doc/design/external_special_remote_protocol.mdwn
@@ -291,14 +291,14 @@ handling a request.
   tracking the size of the file as it grows.)  
   (git-annex does not send a reply to this message.)
 * `DIRHASH Key`  
-  Gets a two level hash associated with a Key. Something like "aB/Cd".
+  Gets a two level hash associated with a Key. Something like "aB/Cd/".
   This is always the same for any given Key, so can be used for eg,
   creating hash directory structures to store Keys in. This is the same
   directory hash that git-annex uses inside `.git/annex/objects/`  
   (git-annex replies with VALUE followed by the value.)
 * `DIRHASH-LOWER Key`  
   Gets a two level hash associated with a Key, using only lower-case.
-  Something like "abc/def".
+  Something like "abc/def/".
   This is always the same for any given Key, so can be used for eg,
   creating hash directory structures to store Keys in. This is the same
   directory hash that is used by eg, the directory special remote.  

diff --git a/doc/design/external_special_remote_protocol/comment_51_c0eaa8639ad2b21ac917d9033d77a327._comment b/doc/design/external_special_remote_protocol/comment_51_c0eaa8639ad2b21ac917d9033d77a327._comment
new file mode 100644 (file)
index 0000000..449ae3a
--- /dev/null
+++ b/doc/design/external_special_remote_protocol/comment_51_c0eaa8639ad2b21ac917d9033d77a327._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""Re: DIRHASH ending in slash?"""
+ date="2022-09-30T17:31:25Z"
+ content="""
+Hmm, so it does. This would not have been my choice for ideal behavior, but
+I don't want to break things that depend on it now. 
+So I've updated the documentation.
+"""]]