From 62eb69e079db0232bd7358dc71f615900b0ff0d3 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sat, 30 Mar 2013 18:01:29 +0000 Subject: [PATCH] Added a comment --- ...comment_5_359b80948ac92a0f1eb695599456486c._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/three_character_directories_created/comment_5_359b80948ac92a0f1eb695599456486c._comment diff --git a/doc/bugs/three_character_directories_created/comment_5_359b80948ac92a0f1eb695599456486c._comment b/doc/bugs/three_character_directories_created/comment_5_359b80948ac92a0f1eb695599456486c._comment new file mode 100644 index 0000000000..6942efe529 --- /dev/null +++ b/doc/bugs/three_character_directories_created/comment_5_359b80948ac92a0f1eb695599456486c._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 5" + date="2013-03-30T18:01:28Z" + content=""" +Clearly this can happen if the git-annex branch is merged into the master branch. I cannot think of any valid reason to want to do that. reset --hard git-annex would also do it; ditto. + +Inclined to close this bug as user error; I'm pretty sure git-annex does not contain a bug that makes it merge in the git-annex branch on its own. Basically the only change that could be made to git-annex to prevent this kind of user error is to move the git-annex branch so it's not under refs/heads, and so is not a visible branch. But then `git push` would not push it either, which needs to happen. +"""]]