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

Re: rebase failure if commit message looks like a patch

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 27, 2009, 18:15 UTC
Message-ID
<alpine.DEB.1.00.0901271914130.3586@pacific.mpi-cbg.de>
In-Reply-To
<loom.20090127T173025-125@post.gmane.org>
Hi,
On Tue, 27 Jan 2009, Anton wrote:
> I have found a strange behaviour of "git rebase", present in following 
> versions:

That is a known issue. Please work around it with redoing the rebase with -m.

I could imagine that we should scan the commit messages before actually running rebase, and either activate -m, or escape the "diff" with a backslash (as is frequently done with "From" in mails).

Ciao, Dscho

Previous: Anton
Message 2 of 2 in “rebase failure if commit message looks like a patch”
  1. AntonJan 27, 2009
  2. Johannes SchindelinJan 27, 2009

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.