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

Re: [PATCH] git-rebase--interactive: Handle commit messages that end in backslash

From
CLChris Lamb <lamby@debian.org>
Date
May 13, 2010, 12:58 UTC
Message-ID
<20100513135807.548594f9@bobcat.office>
In-Reply-To
<20100513133955.05493175@bobcat.office>
Chris Lamb wrote:
 
> This patch fixes three issues with handling commits that end in a
> backslash character ("\"), two of which had potential for silent data
> "loss".

Disregard the patch; it has some funky side-effect which breaks ONTO parsing and I don't know why.

(The problem still exists though.)
Regards,
-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org
       `-
Previous: Chris LambNext: Jeff King
Message 2 of 4 in “git-rebase--interactive: Handle commit messages that end in backslash”
  1. git-rebase--interactive: Handle commit messages that end in backslashChris Lamb, May 13, 2010
  2. Chris LambMay 13, 2010
  3. Jeff KingMay 13, 2010
  4. Thomas RastMay 14, 2010

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.