From 19bb2dcebc981f0a9462a13b84c7f82962f3f59c Mon Sep 17 00:00:00 2001 From: "https://openid.stackexchange.com/user/a7a90689-747e-42ae-87cd-40bcee2b4ade" Date: Wed, 4 Dec 2013 14:53:54 +0000 Subject: [PATCH] --- doc/bugs/git_annex_lock_dangerous.mdwn | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/git_annex_lock_dangerous.mdwn diff --git a/doc/bugs/git_annex_lock_dangerous.mdwn b/doc/bugs/git_annex_lock_dangerous.mdwn new file mode 100644 index 0000000000..f7b2047843 --- /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