From 43a1df8d5d10d9cb9e04848df881ed0fdc7218ec Mon Sep 17 00:00:00 2001 From: jeroen Date: Wed, 28 Sep 2022 11:58:57 +0000 Subject: [PATCH] Added a comment: DIRHASH ending in slash? --- .../comment_50_fdd9804134e6fe5e6527f35fc782cb80._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/design/external_special_remote_protocol/comment_50_fdd9804134e6fe5e6527f35fc782cb80._comment diff --git a/doc/design/external_special_remote_protocol/comment_50_fdd9804134e6fe5e6527f35fc782cb80._comment b/doc/design/external_special_remote_protocol/comment_50_fdd9804134e6fe5e6527f35fc782cb80._comment new file mode 100644 index 0000000000..023d8435dc --- /dev/null +++ b/doc/design/external_special_remote_protocol/comment_50_fdd9804134e6fe5e6527f35fc782cb80._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="jeroen" + avatar="http://cdn.libravatar.org/avatar/72187d05d3414dc8e5766c5575a2d255" + subject="DIRHASH ending in slash?" + date="2022-09-28T11:58:56Z" + content=""" +DIRHASH-LOWER (and I assume the other DIRHASH commands as well) seem to respond with a path ending with a slash. So `VALUE abc/def/` instead of the `VALUE abc/def` example mentioned. `git-annex-remote-rclone` actually assumes the response ends with a slash. Is this indeed what git-annex guarantees? If so, it should probably be documented in this specification. +"""]]