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

Re: [PATCH] add log.fulldiff config option

From
Jeff King <peff@peff.net>
Date
Dec 20, 2006, 08:58 UTC
Message-ID
<20061220085812.GB6895@coredump.intra.peff.net>
In-Reply-To
<7v8xh3j86h.fsf@assigned-by-dhcp.cox.net>
On Wed, Dec 20, 2006 at 12:14:14AM -0800, Junio C Hamano wrote:
> > Also, should this instead be diff.fulldiff?
> 
> Probably not.
Based on your explanation, I think that makes sense.
Show 5 quoted lines
> > Also also, I was going to submit a patch to document --full-diff,
> > but I had a few questions. Should it go in diff-options? That makes some
> > sense to me, but the parsing actually happens in setup_revisions.
> 
> Not at all.

Then where should it go? whatchanged and log have a great deal of overlap in terms of parsing, but they don't seem to share any documentation (or note the fact that git-whatchanged is basically just git-log -p).

> > Furthermore, it seems to do the same thing as --pickaxe-all. Should we
> > try to combine these?
> 
> No.

Thanks for the thorough explanation. I think this makes my config option description a little bit off, then, since it doesn't actually show all of the changed files for a commit in the case of pickaxe.

What has me confused, then, is that you said this:
Show 7 quoted lines
> I typically do:
> 
>         git log --full-diff -p -SCOLLISION
> 
> The --full-diff option helps because it shows the diff for other
> files (that do not have different number of substring COLLISION
> in the pre and postimage) in the same commit as well.

But that isn't the case, AFAIK (e.g., the command line you mention shows only changes to sha1_file.c in commit aac17941, but cache.h was also changed). Did you mean --pickaxe-all?

> Your understanding needs to be clarified on how paths are
> filtered, and how log family and diff interacts, and probably
> these need to be better documented.

To be honest, I'm not sure when one would really _want_ the flexibility this provides. It might be more intuitive to git-{log,whatchanged} users to have a single option (config and command line) to set --full-diff and --pickaxe-all together. At the very least, I think I now want a diff.pickaxeall config option.

Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 6 in “add log.fulldiff config option”
  1. add log.fulldiff config optionJeff King, Dec 20, 2006
  2. Junio C HamanoDec 20, 2006
  3. revision: add --no-full-diff command line optionJeff King, Dec 20, 2006
  4. Junio C HamanoDec 20, 2006
  5. Jeff KingDec 20, 2006
  6. Junio C HamanoDec 20, 2006

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.