On Wed, Mar 18, 2015 at 2:28 PM, Jeff King <p...@peff.net> wrote: > On Wed, Mar 18, 2015 at 05:17:16PM -0400, Jeff King wrote: > >> [1] The double-CR fix works because we strip a single CR from the end of >> the line (as a convenience for CRLF systems), and then the remaining >> CR is syntactically significant. But I am surprised that quoting >> like: >> >> printf '"Icon\r"' >.gitignore >> >> does not seem to work. > > Answering myself: we don't do quoting like this in .gitignore. We allow > backslashing to escape particular characters, like trailing whitespace. > So in theory: > > Icon\\r > > (where "\r" is a literal CR) would work. But it doesn't, because the > CRLF chomping happens separately, and CR is therefore a special case. I > suspect you could not .gitignore a file with a literal LF in it at all > (and I equally suspect that nobody cares in practice).
What does the Icon^M try to catch, exactly? Is it a file? Is it a directory? Is it "anything that begins with Icon^M"? I am wondering if we need an opposite of '/' prefix in the .gitignore file to say "the pattern does not match a directory, only a file". -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
