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

git log: why are --full-diff and --pickaxe-all separate options?

From
Jay Soffian <jaysoffian@gmail.com>
Date
Mar 24, 2010, 15:52 UTC
Message-ID
<76718491003240852m2a2c12afjca2c71f6c78b2047@mail.gmail.com>
I just did this:
$ git log -p -- /some/path

And didn't get the full commit. I know about the --pickaxe-all option, so I optimistically tried:

$ git log -p --pickaxe-all -- /some/path

Which of course, does not do what I want. Eventually I found in the man page that I can do this:

$ git log -p --full-diff -- /some/path

But now I wonder why these are separate options. Is there any reason they shouldn't be unified?

Regardless, perhaps --pickaxe-all without -S and --full-diff without -p should be errors?

j.
Next: Jeff King
Message 1 of 3 in “git log: why are --full-diff and --pickaxe-all separate options?”
  1. Jay SoffianMar 24, 2010
  2. Jeff KingMar 24, 2010
  3. Junio C HamanoMar 24, 2010

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.