From a886d92bcadfd55deb42ebc6210e5f50570f4458 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 29 Jan 2016 13:48:07 -0400 Subject: [PATCH] comment --- ...mment_8_1bad17001364d192e0d9affe5f0ea554._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Git_annex_hangs/comment_8_1bad17001364d192e0d9affe5f0ea554._comment diff --git a/doc/forum/Git_annex_hangs/comment_8_1bad17001364d192e0d9affe5f0ea554._comment b/doc/forum/Git_annex_hangs/comment_8_1bad17001364d192e0d9affe5f0ea554._comment new file mode 100644 index 0000000000..e0d360f371 --- /dev/null +++ b/doc/forum/Git_annex_hangs/comment_8_1bad17001364d192e0d9affe5f0ea554._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 8""" + date="2016-01-29T17:47:02Z" + content=""" +This was fixed in git-annex back in January 2015. It now checks the git +version at runtime, not assuming it will be used with as recent a version +of git as was available at compile time. + +So if you're still seeing this problem, upgrading git-annex or git is the only +solution. +"""]]