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

fsck: When a key is not previously known in the location log, record something so that reinject --known will work.

Browse source
This commit is contained in:
Joey Hess 2016-05-10 13:20:45 -04:00
parent 9169234c34
commit ae65aecb0b
Failed to extract signature
3 changed files with 30 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/forum/Making_a_git-annexy_symlink___34__known__34____63__/comment_1_e04edbe950a41887c4c11a226ca77dce._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2016-05-10T17:04:20Z"
content="""
fsck sees that the (lack of) location
log accurately states that the content is not present, and so avoids
writing to the log.
If fsck always wrote to the log when content was not present, running
fsck in sparse repos would bloat the location logs unncessarily.
But I suppose that it makes sense for fsck to notice that the key
was not known and write to the log in this particular case.
I've gone ahead and made that change.
It's not clear to me though, why this workflow of copying over symlinks,
and adding them and reinjecting is better than just moving over content and
adding it.
"""]]