From 9bcca33ed31d4ee5ebbd1a27bfdce4262f6e65de Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Thu, 24 Apr 2014 18:22:16 +0000 Subject: [PATCH] Added a comment --- .../comment_4_e5a3dc34c6229ec40bc999c3cab28041._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/sync_stages_deletions_on_remote/comment_4_e5a3dc34c6229ec40bc999c3cab28041._comment diff --git a/doc/forum/sync_stages_deletions_on_remote/comment_4_e5a3dc34c6229ec40bc999c3cab28041._comment b/doc/forum/sync_stages_deletions_on_remote/comment_4_e5a3dc34c6229ec40bc999c3cab28041._comment new file mode 100644 index 0000000000..710392daa4 --- /dev/null +++ b/doc/forum/sync_stages_deletions_on_remote/comment_4_e5a3dc34c6229ec40bc999c3cab28041._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.114" + subject="comment 4" + date="2014-04-24T18:22:16Z" + content=""" +git sets bare = false in newly created non-bare repositories. Perhaps this is why? It seems likely that git has an inconsistent default if there's no configuration. Sounds worth filing a bug on git for. OTOH, messing with .git/config in nonstandard ways seems like a good way to cause yourself random pain too. +"""]]