aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
authorGravatar bremner <bremner@web>2015-02-10 18:46:33 +0000
committerGravatar admin <admin@branchable.com>2015-02-10 18:46:33 +0000
commit028a304854a03020a7df3cd804aef25862998ab9 (patch)
treefb01ca32faf6857db1d23502359fed144a469cc8 /doc/bugs
parentcee64f459484215f76e4741aa0f9c93a38361122 (diff)
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/__34__git_annex_metadata__34___without_a_file_name_is_hazardous.mdwn24
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/bugs/__34__git_annex_metadata__34___without_a_file_name_is_hazardous.mdwn b/doc/bugs/__34__git_annex_metadata__34___without_a_file_name_is_hazardous.mdwn
new file mode 100644
index 000000000..1a93b4b5b
--- /dev/null
+++ b/doc/bugs/__34__git_annex_metadata__34___without_a_file_name_is_hazardous.mdwn
@@ -0,0 +1,24 @@
+### Please describe the problem.
+
+Accidentally leaving of the file name when invoking git annex metadata means that
+the changes are applied to all files. This is almost never what I want, and generally leads to either manual work or trying to undo the commit on the git-annex branch.
+
+### What steps will reproduce the problem?
+
+% git annex metadata -s field=value
+
+congrats, your old values of field are (kinda) gone.
+
+### What version of git-annex are you using? On what operating system?
+
+5.20141125, debian
+
+### Please provide any additional information below.
+
+[[!format sh """
+# If you can, paste a complete transcript of the problem occurring here.
+# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
+
+
+# End of transcript or log.
+"""]]