diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/Making_a_git-annexy_symlink___34__known__34____63__/comment_1_e04edbe950a41887c4c11a226ca77dce._comment | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/forum/Making_a_git-annexy_symlink___34__known__34____63__/comment_1_e04edbe950a41887c4c11a226ca77dce._comment b/doc/forum/Making_a_git-annexy_symlink___34__known__34____63__/comment_1_e04edbe950a41887c4c11a226ca77dce._comment new file mode 100644 index 000000000..ad898c5e8 --- /dev/null +++ b/doc/forum/Making_a_git-annexy_symlink___34__known__34____63__/comment_1_e04edbe950a41887c4c11a226ca77dce._comment @@ -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. +"""]] |