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

Re: RFC: Change whatchanged to report changes from merges by default?

From
MBMark Burton <markb@ordern.com>
Date
Dec 20, 2008, 20:21 UTC
Message-ID
<20081220202109.336d0a5e@crow>
In-Reply-To
<7vvdtewqvy.fsf@gitster.siamese.dyndns.org>

On Sat, 20 Dec 2008 12:09:05 -0800 Junio C Hamano <gitster@pobox.com> wrote:

Show 9 quoted lines
> IOW, I consider "whatchanged" a command that is kept only for old timers'
> sake.  There is no reason to promote it, but there is no reason to
> deprecate it, either.  Which means the answer to this question...
> 
> > Would it not make more sense to have git whatchanged show the changes
> > introduced by merges by default and then people can use the (already
> > supported) --no-merges option to suppress that behaviour?  
> 
> ... is a NO spelled in capital letters.
OK (spelled in capital letters), I won't submit the patch.
Cheers,
Mark
Previous: Junio C Hamano
Message 4 of 4 in “RFC: Change whatchanged to report changes from merges by default?”
  1. Mark BurtonDec 20, 2008
  2. Mark BurtonDec 20, 2008
  3. Junio C HamanoDec 20, 2008
  4. Mark BurtonDec 20, 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.