git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug: git-rebase goofs up \n in commit messages

From
Jeff King <peff@peff.net>
Date
May 26, 2007, 07:47 UTC
Message-ID
<20070526074703.GA2563@coredump.intra.peff.net>
In-Reply-To
<20070526073855.GA6395@gondor.apana.org.au>
On Sat, May 26, 2007 at 05:38:55PM +1000, Herbert Xu wrote:
Show 7 quoted lines
> Yep.  Section 2.2.3 says that the backslash within double quotes will
> only serve as an escape character for $, `, ", \ and <newline>.  Of
> course, you can always use a single quote instead, i.e.,
> 
> printf '%s\n' "$VAR"
> 
> Then there can be no doubt :)

Right, I wasn't sure if the single quotes were necessary, but it looks like Junio's version (with doublequotes) is also fine according to POSIX. Thanks again.

-Peff
Previous: Herbert XuNext: Junio C Hamano
Message 12 of 13 in “Bug: git-rebase goofs up \n in commit messages”
  1. Szekeres IstvanMay 25, 2007
  2. Jeff KingMay 26, 2007
  3. Herbert XuMay 26, 2007
  4. Jeff KingMay 26, 2007
  5. Junio C HamanoMay 26, 2007
  6. Junio C HamanoMay 26, 2007
  7. Jeff KingMay 26, 2007
  8. Junio C HamanoMay 26, 2007
  9. Herbert XuMay 26, 2007
  10. Jeff KingMay 26, 2007
  11. Herbert XuMay 26, 2007
  12. Jeff KingMay 26, 2007
  13. Junio C HamanoMay 26, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.