From 9e1ce93eb717a36e5f4264eb03e8da8f46e2772e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 1 Dec 2014 18:37:28 -0400 Subject: comment --- .../comment_3_032d4a64e2f010fcf9359e4f77b6d784._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/git_annex_import_fails_on_filenames_with_newlines_in_them/comment_3_032d4a64e2f010fcf9359e4f77b6d784._comment diff --git a/doc/bugs/git_annex_import_fails_on_filenames_with_newlines_in_them/comment_3_032d4a64e2f010fcf9359e4f77b6d784._comment b/doc/bugs/git_annex_import_fails_on_filenames_with_newlines_in_them/comment_3_032d4a64e2f010fcf9359e4f77b6d784._comment new file mode 100644 index 000000000..184a77af2 --- /dev/null +++ b/doc/bugs/git_annex_import_fails_on_filenames_with_newlines_in_them/comment_3_032d4a64e2f010fcf9359e4f77b6d784._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2014-12-01T22:33:23Z" + content=""" +Mattias seems to be wrong. It may be that some of the shell script parts of +git don't support it, or that parts of git has bugs. But as far as git's +data representation is concerned, \n is a character like any other, and +eg `git add` and `git commit` deal with it just fine. + +(\0 is a different story..) +"""]] -- cgit v1.2.3