From 0784c3e72a7a53b99038c710e58ca66b245f0485 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 13 Mar 2023 13:48:10 -0400 Subject: [PATCH] tag datalad It links to a datalad issue, so I suppose this is right? --- .../init_fails_in_a_folder_with_newline_in_its_name.mdwn | 1 + .../comment_1_2690ed9441685068c291a182d39c2616._comment | 5 ----- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/doc/bugs/init_fails_in_a_folder_with_newline_in_its_name.mdwn b/doc/bugs/init_fails_in_a_folder_with_newline_in_its_name.mdwn index a6d7624f14..cfb2c55bdc 100644 --- a/doc/bugs/init_fails_in_a_folder_with_newline_in_its_name.mdwn +++ b/doc/bugs/init_fails_in_a_folder_with_newline_in_its_name.mdwn @@ -31,3 +31,4 @@ git-annex version: 10.20230214+git26-g8f2829e646-1~ndall+1 as `git` doesn't mind, and now annex batched commands support `-z` already for filenames with newlines in them, I think git-annex should tolerate repository folders with newlines in them too. +[[!tag projects/datalad]] diff --git a/doc/bugs/init_fails_in_a_folder_with_newline_in_its_name/comment_1_2690ed9441685068c291a182d39c2616._comment b/doc/bugs/init_fails_in_a_folder_with_newline_in_its_name/comment_1_2690ed9441685068c291a182d39c2616._comment index 9d5749709b..201c6f93c4 100644 --- a/doc/bugs/init_fails_in_a_folder_with_newline_in_its_name/comment_1_2690ed9441685068c291a182d39c2616._comment +++ b/doc/bugs/init_fails_in_a_folder_with_newline_in_its_name/comment_1_2690ed9441685068c291a182d39c2616._comment @@ -20,9 +20,4 @@ which can get a newline in a value with eg `git annex config --set annex.largefiles "xxx\nyyy"` and the result is that reading the value back out omits the part after the newline. - -Also, a newline in a subdirectory inside the repository breaks -adding files in that directory with `git-annex add`.git- - -Newlines in filenames seem to work ok though... """]]