From 9ad0cab29ab28829324b4b0302c5e9860b2622c9 Mon Sep 17 00:00:00 2001 From: "https://launchpad.net/~arand" Date: Thu, 14 Mar 2013 00:01:27 +0000 Subject: --- ...x_removes_object_even_if_referred_to_by_others.mdwn | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/unannex_removes_object_even_if_referred_to_by_others.mdwn 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 -- cgit v1.2.3