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

Added a comment

Browse source
This commit is contained in:
http://joeyh.name/ 2014-02-06 17:05:46 +00:00 • committed by admin
parent a2f0afcb21
commit 6bb1b2fda5
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/forum/Locking_and_then_unlocking_a_file_results_in_file_changed_warning/comment_3_fd39e6ceffd9bf0709658c34945d8699._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="206.74.132.139"
subject="comment 3"
date="2014-02-06T17:05:45Z"
content="""
Recent versions of git-annex have tried to extend the --force option to be needed in any operation that can possibly cause data loss. This includes locking a file, since that throws away any changes.
Note that `git annex lock` does not check if the file is unmodified. For a few reasons including
* some backends don't include a checksum
* it would be expensive to check a checksum
* the file could get modified after or during a checksum check, and those modifications would be missed
If you are sure you want to throw away any changes, use --force as suggested. If not, use `git annex add $file`, and assuming you're using a checksumming backend, it will notice the file has not changed and do what you want `git annex lock $file` to have done in this case.
"""]]