From 0f9e5ada82a7ba5a3267c67c2b89d8714abfc3c5 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 21 Nov 2021 11:19:47 -0400 Subject: [PATCH] idea --- ...djusted_branch_with_hashdirlower_links.mdwn | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/todo/adjusted_branch_with_hashdirlower_links.mdwn diff --git a/doc/todo/adjusted_branch_with_hashdirlower_links.mdwn b/doc/todo/adjusted_branch_with_hashdirlower_links.mdwn new file mode 100644 index 0000000000..9441ccf4d9 --- /dev/null +++ b/doc/todo/adjusted_branch_with_hashdirlower_links.mdwn @@ -0,0 +1,18 @@ +This would be like enabling the annex.tune.objecthashlower=true +[[tuning]] when creating a repository, but could be done after the fact, +eg when a user needs to clone an existing reppsitory to a filesystem +that has problems with mixed case hash directories. + +The adusted branch would simply convert annex links to use lower-case +hashing, which is easy. But it would also need to enable storing new object +files in lower-case hash directories, and move any currently stored object +files to those directories. + +How to handle a `git checkout master` then? None of the annex links in +master would work. Normally the user can leave an adjusted branch that way, +but if they wanted to leave this one, there would have to be a command +to move everything back. + +Note that, annexLocationsNonBare does fall back to looking for +hashDirLower, so getting files from a repository with this enabled to +another repository should work ok. --[[Joey]]