From 9a22adf358801e2951c84f2b3fe8a6c0677de287 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 30 Sep 2019 13:40:53 -0400 Subject: [PATCH] comment --- ...omment_2_07f9665bf0acea333dafb2db81e87619._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/Q__58___is_there_a_reason_to___34__sense__34___git_annex_post-receive_in_a_hook__63__/comment_2_07f9665bf0acea333dafb2db81e87619._comment diff --git a/doc/bugs/Q__58___is_there_a_reason_to___34__sense__34___git_annex_post-receive_in_a_hook__63__/comment_2_07f9665bf0acea333dafb2db81e87619._comment b/doc/bugs/Q__58___is_there_a_reason_to___34__sense__34___git_annex_post-receive_in_a_hook__63__/comment_2_07f9665bf0acea333dafb2db81e87619._comment new file mode 100644 index 0000000000..22a84f2893 --- /dev/null +++ b/doc/bugs/Q__58___is_there_a_reason_to___34__sense__34___git_annex_post-receive_in_a_hook__63__/comment_2_07f9665bf0acea333dafb2db81e87619._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2019-09-30T17:36:40Z" + content=""" +Of course if you're sure you'll never use an old version of git-annex +(or don't care if the hook breaks if you do), you can modify the hook +script. + +I don't see any changes I should make here, can this bug report be closed? +"""]]