summaryrefslogtreecommitdiff
path: root/doc/bugs/git_annex_lock_dangerous.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/git_annex_lock_dangerous.mdwn')
-rw-r--r--doc/bugs/git_annex_lock_dangerous.mdwn19
1 files changed, 19 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..ae0ff24b6
--- /dev/null
+++ b/doc/bugs/git_annex_lock_dangerous.mdwn
@@ -0,0 +1,19 @@
+### 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
+
+> Agreed; [[done]] --[[Joey]]