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

Re: wrong expectation from "git log -p"

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 2, 2009, 00:54 UTC
Message-ID
<7vzlcrihew.fsf@alter.siamese.dyndns.org>
In-Reply-To
<pan.2009.06.02.00.34.36@fedoraproject.org>
Thomas Spura <tomspur@fedoraproject.org> writes:
Show 8 quoted lines
> If running "git log -p parse-options.*", the last commit is 
> df217ed6430efe444a09fffdafd39720ae3f9864
> There are the changes this commit makes towards parse-options.*.
>
> I was expecting to see the full commit with all changes and not only 
> towards the 2 files - only including the two files.
>
> Is my expactation wrong or is this a bug?
Time to run "man git-log" and look for --full-diff, perhaps?
Previous: Thomas SpuraNext: Todd Zullinger
Message 2 of 6 in “wrong expectation from "git log -p"”
  1. Thomas SpuraJun 2, 2009
  2. Junio C HamanoJun 2, 2009
  3. completion: Add --full-diff to log/gitk optionsTodd Zullinger, Jun 3, 2009
  4. Thomas RastJun 3, 2009
  5. completion: Add --full-diff to log optionsTodd Zullinger, Jun 3, 2009
  6. Eric WongJul 5, 2009

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.