From 3ea72620f1f1b3c1123c504f39b47f5eb6b57e8b Mon Sep 17 00:00:00 2001 From: "https://launchpad.net/~stephane-gourichon-lpad" Date: Mon, 24 Jul 2017 08:06:55 +0000 Subject: Added a comment: User expectations and what git annex unannex does. --- ...ent_3_6c99a97d56b1a3b12092c15fafcf8761._comment | 35 ++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 doc/bugs/unannex__58___Cannot_proceed_with_uncommitted_changes_staged_in_the_index/comment_3_6c99a97d56b1a3b12092c15fafcf8761._comment diff --git a/doc/bugs/unannex__58___Cannot_proceed_with_uncommitted_changes_staged_in_the_index/comment_3_6c99a97d56b1a3b12092c15fafcf8761._comment b/doc/bugs/unannex__58___Cannot_proceed_with_uncommitted_changes_staged_in_the_index/comment_3_6c99a97d56b1a3b12092c15fafcf8761._comment new file mode 100644 index 000000000..47d417cec --- /dev/null +++ b/doc/bugs/unannex__58___Cannot_proceed_with_uncommitted_changes_staged_in_the_index/comment_3_6c99a97d56b1a3b12092c15fafcf8761._comment @@ -0,0 +1,35 @@ +[[!comment format=mdwn + username="https://launchpad.net/~stephane-gourichon-lpad" + nickname="stephane-gourichon-lpad" + avatar="http://cdn.libravatar.org/avatar/02d4a0af59175f9123720b4481d55a769ba954e20f6dd9b2792217d9fa0c6089" + subject="User expectations and what git annex unannex does." + date="2017-07-24T08:06:55Z" + content=""" +# Where we are + +@joey thank you for these explanations, more detailed than when I reported the same problem 8 months ago commenting https://git-annex.branchable.com/git-annex-unannex/ (@tom.prince had already written this page but I did not find it). + +Yet all this happens in a git world, where private history can be rewritten, so *there must be a simpler way*. + +# What people expect from \"undo accidental add command\" + +@tom.prince thanks for explaining what you expected `unannex` to do. Looks like I expected exactly the same behavior. + +IMHO current behavior of `git annex unannex` does not match what people expect of \"undo accidental add command\". + +# What current `git-annex unannex` actually does + +If behavior does not match words, perhaps behavior is interesting but should be matched with different words? + +Looking at what `git-annex unannex`, here are the words that came to mind: + +> git-annex unannex - turn a path which points to annexed content into a plain file that is store in regular git. + +Notice that: + +* `git-annex` retains history +* other paths may still refer to the same content, so the annex may still contain a copy of the same data. Else it becomes unused content subject to `git-annex dropunused`. + +Thank you for your attention. + +"""]] -- cgit v1.2.3