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

Re: [PATCH] I don't known anyone who understands what it means when they do a merge and see "file.txt: needs update". "file.txt: has changes" is much clearer.

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 4, 2008, 09:29 UTC
Message-ID
<alpine.DEB.1.00.0805041027150.30431@racer>
In-Reply-To
<7v3aozwcj6.fsf@gitster.siamese.dyndns.org>
Hi,
On Sat, 3 May 2008, Junio C Hamano wrote:
Show 11 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > On Sat, 3 May 2008, Tim Harper wrote:
> >
> >> -			printf("%s: needs update\n", ce->name);
> >> +			printf("%s: has changes\n", ce->name);
> >
> > How about "local changes"?
> 
> Aren't there Porcelain and end-user scripts that relies on the output by
> doing "sed -ne s'/: needs update$//p"?

Potentially. But I thought that it would make more sense to use --name-only in that case.

However, I obviously like that you go out of your way to cause the least damage to current users, so how about something like in merge-recursive, where you can change some output based on an environment variable?

In this case, I'd rather make it an option, but that may be overkill. But then, enough people have commented that this message is irritating them.

Ciao, Dscho

Previous: Tim HarperNext: Matt Graham
Message 12 of 13 in “I don't known anyone who understands what it means when they do a merge and see "file.txt: needs update". "file.txt: has changes" is much clearer.”
  1. I don't known anyone who understands what it means when they do a merge and see "file.txt: needs update". "file.txt: has changes" is much clearer.Tim Harper, May 3, 2008
  2. Johannes SchindelinMay 3, 2008
  3. Tim HarperMay 3, 2008
  4. Junio C HamanoMay 3, 2008
  5. Tim HarperMay 3, 2008
  6. Junio C HamanoMay 4, 2008
  7. Avery PennarunMay 4, 2008
  8. Junio C HamanoMay 4, 2008
  9. Avery PennarunMay 5, 2008
  10. Jeff KingMay 5, 2008
  11. Tim HarperMay 6, 2008
  12. Johannes SchindelinMay 4, 2008
  13. Matt GrahamMay 3, 2008

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.