mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

followup

Browse source
This commit is contained in:
Joey Hess 2022-05-09 16:10:31 -04:00
parent 136ad17b94
commit 3b83224e57
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/todo/command_to___34__migrate__34___from_adjusted_mode.mdwn
View file

@ -3,3 +3,5 @@ Checking out `master` branch is not sufficient since `.git/annex/objects` uses d
[[!meta author=yoh]]
[[!tag projects/datalad]]
[[!meta title="command to migrate object files from hashdirlower to hashdirmixed"]]

20
doc/todo/command_to___34__migrate__34___from_adjusted_mode/comment_3_4375a63a864306c39323fa4b159425d6._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2022-05-09T19:54:35Z"
content="""
Ok, so the object location usually used in bare repositories..
One way that could happen is if core.symlinks=false and
annex.crippledfilesystem=true. Then it does use the bare form of object
filenames, which is kind of ok since it's not going to be using symlinks in
that repository.
Also, before 2016, git-annex used those names whenever annex.crippledfilesystem=true,
no matter what core.symlinks was set to. So if the files are that old..
This does seem to point to there needing to be a way to migrate the object
files in a repository to the right names. It might be a reasonable thing
for git-annex fsck to do, when it sees a symlink to an object file that
is in the other location.
"""]]