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

Re: log -p hides changes in merge commit

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 7, 2011, 20:27 UTC
Message-ID
<7vk4ig5uib.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4D276926.2020407@cfl.rr.com>
Phillip Susi <psusi@cfl.rr.com> writes:
> That does help me understand the difference between -c and -cc, but I
> still don't see why one or the other is not the default behavior of log
> -p, instead of opting to never show anything at all for merges?

Assuming this is about the default, the answer is very simple. The features to support -c and --cc came _much_ later than -p, and many people have got used to the default behaviour after using "log -p" for a long time. It simply is rude to change the default on them.

As -c or --cc won't do anything special on a non-merge commit, you can always say "log -p --cc" if that output is what you want to see.

Previous: Phillip Susi
Message 6 of 6 in “log -p hides changes in merge commit”
  1. Phillip SusiJan 6, 2011
  2. Junio C HamanoJan 6, 2011
  3. Phillip SusiJan 6, 2011
  4. Jonathan NiederJan 6, 2011
  5. Phillip SusiJan 7, 2011
  6. Junio C HamanoJan 7, 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.