summaryrefslogtreecommitdiff
path: root/doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_1_beb674205f06310f6a9060bea35fa3fe._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_1_beb674205f06310f6a9060bea35fa3fe._comment')
-rw-r--r--doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_1_beb674205f06310f6a9060bea35fa3fe._comment11
1 files changed, 0 insertions, 11 deletions
diff --git a/doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_1_beb674205f06310f6a9060bea35fa3fe._comment b/doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_1_beb674205f06310f6a9060bea35fa3fe._comment
deleted file mode 100644
index 8ee885b5f..000000000
--- a/doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_1_beb674205f06310f6a9060bea35fa3fe._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 1"
- date="2013-12-05T20:14:54Z"
- content="""
-There was a bug in 5.20131118 through 5.20131127 that caused git-annex init, when run in a bare repository, to set core.bare=false. This would also happen
-if you had a bare repository that had not been initted, and ran some otherwise innocuous command like git-annex status in it (since git-annex can auto-init).
-
-The most recent version you say is broken, 5.20131130-gc25be33, is right at the commit where I fixed that bug. But before I taught git-annex to automatically fix up a repository that it had done this to. You can get that fix in the current daily builds, or you can just run `git config core.bare true` to fix the setting, and version 5.20131130-gc25be33 shouldn't screw it up again.
-"""]]