From 210ae7da87ab38ff777514cd57605021adeb3623 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawn2MI-Ci-bS9W5NITngsBJiL8LqWYcJ458" Date: Mon, 23 Feb 2015 11:44:36 +0000 Subject: --- doc/bugs/unannex_requires_commit_for_new_directories.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/bugs/unannex_requires_commit_for_new_directories.mdwn') diff --git a/doc/bugs/unannex_requires_commit_for_new_directories.mdwn b/doc/bugs/unannex_requires_commit_for_new_directories.mdwn index 9f2ad1134..0f56d59e8 100644 --- a/doc/bugs/unannex_requires_commit_for_new_directories.mdwn +++ b/doc/bugs/unannex_requires_commit_for_new_directories.mdwn @@ -1,5 +1,5 @@ ### Please describe the problem. -"git-annex unannex" requires an unexpected (and undesirable) commit only when adding files in a new directory. This undesirable because whenever "git-annex add" is accidentally run in a new directory, the only way to undo it is to commit first and then unannex, which adds two unwanted commits to the git log. Moreover, this behavior is not consitent with unannex on files in non-new directories: in that case unannex works as expected. +"git-annex unannex" requires an unexpected (and undesirable) commit only when adding files in a new directory. This is undesirable because whenever "git-annex add" is accidentally run in a new directory, the only way to undo it is to commit first and then unannex, which adds two unwanted commits to the git log. Moreover, this behavior is not consistent with unannex on files in non-new directories: in that case unannex works as expected. ### What steps will reproduce the problem? 
/tmp> mkdir test
-- 
cgit v1.2.3