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

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

From
MBMark Burton <markb@ordern.com>
Date
Dec 20, 2008, 10:42 UTC
Message-ID
<20081220104232.5ff1b7c0@crow>
Hi,

Is it just an accident of history or by design that whatchanged requires the -m option to show changes introduced by merges but diff and git log show those changes without requiring any extra options?

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?

It appears that just setting rev.ignore_merges to 0 in cmd_whatchanged() would do the trick. Shall I submit a patch?

Mark
Next: Mark Burton
Message 1 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.