From 471ea17ae3eb77d9104a8be9c4d96f16ed9a737a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 21 Jul 2023 15:33:59 -0400 Subject: [PATCH] comment --- ..._73c1495abff5284c42a8cf0537b19df4._comment | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 doc/bugs/list__58___escaped_characters_not_accepted_as_input/comment_4_73c1495abff5284c42a8cf0537b19df4._comment diff --git a/doc/bugs/list__58___escaped_characters_not_accepted_as_input/comment_4_73c1495abff5284c42a8cf0537b19df4._comment b/doc/bugs/list__58___escaped_characters_not_accepted_as_input/comment_4_73c1495abff5284c42a8cf0537b19df4._comment new file mode 100644 index 0000000000..6c05d50aa8 --- /dev/null +++ b/doc/bugs/list__58___escaped_characters_not_accepted_as_input/comment_4_73c1495abff5284c42a8cf0537b19df4._comment @@ -0,0 +1,26 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2023-07-21T19:20:54Z" + content=""" +Interestingly, `git rm` does have a way to make it accept quotepath +formatted filenames: + + --pathspec-from-file= + Pathspec is passed in instead of commandline args. If + is exactly - then standard input is used. Pathspec elements are + separated by LF or CR/LF. Pathspec elements can be quoted as + explained for the configuration variable core.quotePath (see git- + config(1)). See also --pathspec-file-nul and global + --literal-pathspecs. + +I don't think that's the first thing I would have reached for though. +It's not a common option supported by other git commands. I would have +probably instead used `git ls-files -c core.quotePath=false`, filtered +the output to only have one of the two related filenames, and passed it to +`git rm` as a parameter. + +If git had a common way to accept quotepath input, I'd think that git-annex +should support it, but since it doesn't, I'm unsure that it's worth complicating +git-annex, since core.quotePath=false can already be used. +"""]]