From 3b44ea01f59d2ed29be7593f1e2a0dfc570019e5 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 13 Nov 2017 13:11:06 -0400 Subject: [PATCH] update; git bug fixed in pu --- ...omment_6_19c9dbdbcc2875cd6429f0ba06336fd2._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_6_19c9dbdbcc2875cd6429f0ba06336fd2._comment diff --git a/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_6_19c9dbdbcc2875cd6429f0ba06336fd2._comment b/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_6_19c9dbdbcc2875cd6429f0ba06336fd2._comment new file mode 100644 index 0000000000..11d32e5f67 --- /dev/null +++ b/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_6_19c9dbdbcc2875cd6429f0ba06336fd2._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 6""" + date="2017-11-13T17:09:31Z" + content=""" +The git bug is fixed in git's `pu` branch, or as Peff says, +at least "papered over", and I've tested the fix with git-annex and +it seems to avoid the problem. So as long as +5eb0e541132208a9027cc090943276fa52f29c71 gets into a git release, +this bug can be closed without any changes to git-annex. +"""]]