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 6, 2011, 19:43 UTC
Message-ID
<7vwrmhakdz.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4D25F6BE.7010300@cfl.rr.com>
Phillip Susi <psusi@cfl.rr.com> writes:
> It seems that adding -c or --cc to the log correctly shows the change to
> a, but why is this not shown by default?

Depends on the definition of "correctly", but perhaps you have a definition different from ours ;-) The "patches" shown with -c/--cc are designed to be different from normal diff so that people do not accidentally try to apply them with "patch" or "git apply".

"log -p" omits merge commits by default because diffs of merges are mostly not useful for ordinary purposes. If you are trying to use "log -p" to reproduce a (part of) history, perhaps you would want to also study -m option.

Previous: Phillip SusiNext: Phillip Susi
Message 2 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.