summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://launchpad.net/~arand <arand@web>2013-03-14 00:01:27 +0000
committerGravatar admin <admin@branchable.com>2013-03-14 00:01:27 +0000
commit9ad0cab29ab28829324b4b0302c5e9860b2622c9 (patch)
treeff5dc6ab4080dbff1a170ff9643d0cbac574935a
parente9b3341e8bee8c052f664a1c95e2b185ae677a23 (diff)
-rw-r--r--doc/bugs/unannex_removes_object_even_if_referred_to_by_others.mdwn18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others.mdwn b/doc/bugs/unannex_removes_object_even_if_referred_to_by_others.mdwn
new file mode 100644
index 000000000..69a4496fe
--- /dev/null
+++ b/doc/bugs/unannex_removes_object_even_if_referred_to_by_others.mdwn
@@ -0,0 +1,18 @@
+##What steps will reproduce the problem?
+
+ echo text > foo
+ echo text > bar
+ git annex add foo bar
+ git annex unannex foo
+
+##What is the expected output? What do you see instead?
+
+I would expect that the object behind 'bar' remained intact, what happens is that the object is moved out of the annex and 'bar' is left as a dangling symlink, if you are unlucky and don't spot this, it could be potentially dangerous, since you can easily lose data.
+
+##What version of git-annex are you using? On what operating system?
+
+git-annex built from git on Tue Mar 12 15:58:36 2013 -0400
+
+From commit: 70b7555eaf9ac5f88bb137985d93bed8d5a434e8
+
+On Debian Sid