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

Re: commit message parsing error in rebase

From
Csaba Henk <csaba@lowlife.hu>
Date
May 4, 2012, 19:24 UTC
Message-ID
<CAA-jfp=yMVFrfFgh9A_zNC5nG8PTvNWBRpkbpbVK+7GUU7jO9Q@mail.gmail.com>
In-Reply-To
<7vlil7ah5w.fsf@alter.siamese.dyndns.org>
On Sat, May 5, 2012 at 12:48 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Sorry, but we do not support writing "diff" output in log message as-is
> (it is primarily because format-patch output from such a commit is hard to
> read for humans).  A common workaround is to indent such an illustrative
> patches indented in the log message.

In that case, would it not be wise to be explicit about that and warn or err if such a commit is attempted?

Csaba
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 4 in “commit message parsing error in rebase”
  1. Csaba HenkMay 4, 2012
  2. Junio C HamanoMay 4, 2012
  3. Csaba HenkMay 4, 2012
  4. Junio C HamanoMay 4, 2012

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.