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

Re: Merge made by recursive?

From
Jeff King <peff@peff.net>
Date
May 25, 2011, 19:50 UTC
Message-ID
<20110525195032.GC27260@sigill.intra.peff.net>
In-Reply-To
<7vvcwy37de.fsf@alter.siamese.dyndns.org>
On Wed, May 25, 2011 at 12:30:53PM -0700, Junio C Hamano wrote:
Show 7 quoted lines
> I think so.  An earlier version of "git merge" used to say something like:
> 
>     Committed merge ..., made by resolve.
> 
> back in Sept 2005, so it is not so recent development. If we change it
> now, scripts in thousands of existing users hands might cringe instead,
> though.

I was going to say "those scripts are stupid and broken for parsing stderr", but:

  1. We actually write this (and many other diagnostic messages) to
     stdout, not stderr. That seems weird and unusual.
  2. The message ends up in the reflog.

Also, most of the rest of the merge output has been gettext-ized, but not this message. If we are going to declare it not parseable, should we also be internationalizing it?

-Peff
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 10 in “Merge made by recursive?”
  1. Shawn LigockiMay 25, 2011
  2. Ramkumar RamachandraMay 25, 2011
  3. Jakub NarebskiMay 25, 2011
  4. Junio C HamanoMay 25, 2011
  5. Jeff KingMay 25, 2011
  6. Junio C HamanoMay 25, 2011
  7. Junio C HamanoMay 25, 2011
  8. Jeff KingMay 25, 2011
  9. Jeff KingMay 25, 2011
  10. Jeff KingMay 25, 2011

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.