From 7a176b3e49f9af5878d55028d1eacc13e2b97225 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnx8kHW66N3BqmkVpgtXDlYMvr8TJ5VvfY" Date: Thu, 26 Mar 2015 20:38:05 +0000 Subject: [PATCH] --- ...ed_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load.mdwn | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load.mdwn diff --git a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load.mdwn b/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load.mdwn new file mode 100644 index 0000000000..df42a49066 --- /dev/null +++ b/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load.mdwn @@ -0,0 +1,4 @@ +### Please describe the problem. + +Current layout is DIRHASH (of two levels) /KEY/KEY, so I would need to hardcode having that KEY directory. It might be nice to either make DIRHASH to return full hash directory (but it might break existing special remotes), or supplement with e.g. DIRHASHFULL which would return all the levels necessary to reach the KEY file +