From a8580992720f8d8090fd8b2a8c97313640e3f37a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 31 Mar 2023 14:18:50 -0400 Subject: [PATCH] clarify --- .../comment_1_2690ed9441685068c291a182d39c2616._comment | 3 +++ 1 file changed, 3 insertions(+) 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 949bee65a5..284eea755d 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 @@ -14,4 +14,7 @@ written to uuid.log contains a newline, which prevents parsing that line of the log correctly. This can also be seen by passing a value with a newline to `git-annex describe`. It would also happen in the case with the newline directory if it didn't fail earlier. + +Also fixed this, though, with a one-way escaping, +see [[!commit 38e9ea8497bb2ab058e5bd46a666857789c0a84d]]. """]] -- 2.30.2