diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-01-06 21:32:43 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-01-06 21:32:43 -0400 |
| commit | def6ca054e8265a1f3aa394d281b37f58d667520 (patch) | |
| tree | df6ea22f33178bd4586833786a21f23288a4828b | |
| parent | 8e7de0104702d59e327694451303e8fbe53c9ea5 (diff) | |
| parent | 773af32ee4250ec4101ac64816c25c0f51aa118b (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
| -rw-r--r-- | doc/forum/unlock__47__lock_always_gets_me.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/forum/unlock__47__lock_always_gets_me.mdwn b/doc/forum/unlock__47__lock_always_gets_me.mdwn new file mode 100644 index 000000000..0891eed0e --- /dev/null +++ b/doc/forum/unlock__47__lock_always_gets_me.mdwn @@ -0,0 +1,11 @@ +Several times now I've done something like: + + $ git annex unlock movie.avi + $ mv /tmp/fixed.avi movie.avi + $ git annex lock movie.avi + +Oops, I just lost my fixed.avi! That really feels like the right sequence of operations to me, so I'm always surprised when I make that mistake. I would like to see the current `lock` renamed to something like `undo-unlock`, or have the behavior changed to be the same as `add`, or maybe warn and require a `--force` when the file has been changed. + +If changing current behavior is undesirable, maybe `unlock` could just print a reminder that `git annex add` is the correct next step after making changes? + +Failing that, I suppose I could slowly start to learn from my mistakes. |