From fb8fdec166d5a738e235353d874f6207a94539e7 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 27 May 2016 11:05:53 -0400 Subject: followup --- ...comment_4_d26052bc19fbb6eaa84b2d72c280f11a._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/Whereis_reports_same_UUID_multiple_times/comment_4_d26052bc19fbb6eaa84b2d72c280f11a._comment (limited to 'doc') diff --git a/doc/bugs/Whereis_reports_same_UUID_multiple_times/comment_4_d26052bc19fbb6eaa84b2d72c280f11a._comment b/doc/bugs/Whereis_reports_same_UUID_multiple_times/comment_4_d26052bc19fbb6eaa84b2d72c280f11a._comment new file mode 100644 index 000000000..92f711ed6 --- /dev/null +++ b/doc/bugs/Whereis_reports_same_UUID_multiple_times/comment_4_d26052bc19fbb6eaa84b2d72c280f11a._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2016-05-27T15:02:05Z" + content=""" +In git-annex version 5.20140606, we have: + + * Windows: Fix bug introduced in last release that caused files + in the git-annex branch to have lines teminated with \r. + +There was only 1 week where git-annex had that bug AFAIK, but of +course the broken version could have kept on being used for some time. + +It's also always possible that this same problem popped up again in the +code. The fix in 1ab3d7c81049e4ce7e8e47800e2ef1fecb3a9ab4 was to +Annex.Journal and that still seems ok. The merge code is another place +this could perhaps happen. +"""]] -- cgit v1.2.3