diff options
| author |  https://openid.stackexchange.com/user/a7a90689-747e-42ae-87cd-40bcee2b4ade <Diggory@web> | 2013-12-04 14:53:54 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-12-04 14:53:54 +0000 |
| commit | b2c5be989676b621d36585158799aa31b5604e02 (patch) | |
| tree | 6415af52d9cebf80f98818545f8e1323fde00120 | |
| parent | af016343f3ef1035bf4abccaa17e9caa310f98b6 (diff) | |
| -rw-r--r-- | doc/bugs/git_annex_lock_dangerous.mdwn | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_lock_dangerous.mdwn b/doc/bugs/git_annex_lock_dangerous.mdwn new file mode 100644 index 000000000..f7b204784 --- /dev/null +++ b/doc/bugs/git_annex_lock_dangerous.mdwn @@ -0,0 +1,17 @@ +### Please describe the problem. + +Git annex lock discards data without --force; this is misleading from the name. + +### What steps will reproduce the problem? + + git annex unlock something.txt + kwrite something.txt # edit + git annex lock something.txt # lock is the opposite of unlock, right? + +Oops, just lost my changes! + +If you want my opinion, `git annex lock` should either require `-f` to throw away data or should be renamed (e.g. to `revert` or `checkout`). + +### What version of git-annex are you using? On what operating system? + +git version 1.8.1.2, git-annex version: 4.20130815, Kubuntu 13.04 |