diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck <Jim@web> | 2012-01-06 22:14:35 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2012-01-06 22:14:35 +0000 |
| commit | 773af32ee4250ec4101ac64816c25c0f51aa118b (patch) | |
| tree | d7feb31d17b0fc49f5f93524dadd6a85fe596db7 | |
| parent | b59759e33cda492b6cff67559391b65039ca66f3 (diff) | |
| -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. |