summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2012-10-28 17:13:32 +0000
committerGravatar admin <admin@branchable.com>2012-10-28 17:13:32 +0000
commit9600c62cef11809a32a86cc48824a647f87fcc44 (patch)
treefed6300987530a6acf0edee4a8296852608ea126
parentf759a557d53386ee63a1f3e73480a7ab4911ff33 (diff)
Added a comment
-rw-r--r--doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_1_2eb20b65582fa7f271b1d0bb5560d08c._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_1_2eb20b65582fa7f271b1d0bb5560d08c._comment b/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_1_2eb20b65582fa7f271b1d0bb5560d08c._comment
new file mode 100644
index 000000000..712657e82
--- /dev/null
+++ b/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_1_2eb20b65582fa7f271b1d0bb5560d08c._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="2001:4978:f:21a::2"
+ subject="comment 1"
+ date="2012-10-28T17:13:32Z"
+ content="""
+You can avoid this by not using a deduplicating backend; for example you can use the WORM backend.
+
+However, the foot shooting actually occurs due to using drop --force, which is explicitly asking git-annex to be unsafe. If you want to be safe, simply don't use --force. If you want to safely delete a file, simply `git rm` it, and then `git annex unused` will come along and find content that can safely be removed.
+"""]]