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

Re: [PATCH] Teach 'git apply' to look at $GIT_DIR/config

From
Junio C Hamano <junkio@cox.net>
Date
Feb 18, 2007, 01:03 UTC
Message-ID
<7vsld4p99g.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.63.0702180135240.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 9 quoted lines
> On Sat, 17 Feb 2007, Junio C Hamano wrote:
> ...
>> But I think Jeff is right.  It would make sense to let apply
>> and perhaps 'diff', if we can somehow merge 'diff2' into it,
>> still read from $HOME/.gitconfig if available.
>
> Yes, especially if you are soo used to colours as I grew to be used to 
> them. This was literally one of the reasons I wrote diff2 in the first 
> place. Another was --color-words.
True.  Paches welcome ;-).
Show 12 quoted lines
> BTW any good ideas how to make diff fall back to diff2, so that no similar 
> case falls back to diff-index?
>
> I am really wondering if you can have a syntax which Does The Right Thing 
> at all times. Maybe we can teach diff that exactly two arguments, which 
> both exist in the filesystem, and at least one of them is not tracked, 
> then please use diff2? I wonder how often you do something like
>
> 	git diff object.c object-refs.c
>
> and how confusing it would be that it could mean two things, diff2 _and_ 
> diff-index?
I _think_ the case I would want to use diff2 are:
 (1) I am totally outside a git repository.
or
 (2) I am inside a git repository but I want to compare two
     specific managed files, say GIT-VERSION-GEN and
     git-gui/GIT-VERSION-GEN.

Now, (1) can be had by moving the RUN_SETUP bit out of entry for "diff" in git.c, and do it only when we know we are in a repo (maybe using "setup gently"). If we are outside of a repository, any of the existing diff-* brothers do not make much sense --- we can always do diff2.

For (2), I _think_ it may be useful sometimes but not very often, so how about a specific option that you require upfront?

	git diff --fs --color-words GIT-VERSION-GEN git-gui/GIT-VERSION-GEN
I can do almost that with
	git diff --color-words :GIT-VERSION-GEN :git-gui/GIT-VERSION-GEN

but, it compares indexed ones, not from the working tree, so it is not exactly the same. However, the difference may not make practical difference in this particular example, though. When I want to know the differences between two tracked files, it is usually becausel I want to see if there are similarities to be consolidated, and I would do that before starting to alter working tree files.

Also, strictly speaking, there is third one:
 (3) I am inside a git repository but I want to compare files
     that do not have anything to do with the project I am
     currently working on:
	git diff --fs /etc/skel/profile $HOME/.profile

while I do not think this usage makes any sense, an explicit flag upfront saves you from wondering what the user meant.

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 35 of 49 in “Teach core.autocrlf to 'git apply'”
  1. Teach core.autocrlf to 'git apply'Junio C Hamano, Feb 17, 2007
  2. Teach 'git apply' to look at $GIT_DIR/configJunio C Hamano, Feb 17, 2007
  3. Jeff KingFeb 17, 2007
  4. Junio C HamanoFeb 17, 2007
  5. Jeff KingFeb 17, 2007
  6. Linus TorvaldsFeb 19, 2007
  7. Shawn O. PearceFeb 19, 2007
  8. Junio C HamanoFeb 19, 2007
  9. Linus TorvaldsFeb 19, 2007
  10. Junio C HamanoFeb 19, 2007
  11. Linus TorvaldsFeb 20, 2007
  12. Junio C HamanoFeb 20, 2007
  13. Johannes SchindelinFeb 20, 2007
  14. Junio C HamanoFeb 20, 2007
  15. Johannes SchindelinFeb 20, 2007
  16. git-apply: require -p<n> when working in a subdirectory.Junio C Hamano, Feb 20, 2007
  17. apply: fix memory leak in prefix_one()Johannes Schindelin, Feb 20, 2007
  18. Junio C HamanoFeb 20, 2007
  19. Johannes SchindelinFeb 20, 2007
  20. git-apply: do not lose cwd when run from a subdirectory.Junio C Hamano, Feb 20, 2007
  21. Junio C HamanoFeb 20, 2007
  22. Linus TorvaldsFeb 20, 2007
  23. Daniel BarkalowFeb 21, 2007
  24. Junio C HamanoFeb 21, 2007
  25. Daniel BarkalowFeb 21, 2007
  26. Linus TorvaldsFeb 21, 2007
  27. Junio C HamanoFeb 21, 2007
  28. git-apply: notice "diff --git" patch againJunio C Hamano, Feb 21, 2007
  29. git-apply: guess correct -p<n> value for non-git patches.Junio C Hamano, Feb 22, 2007
  30. Johannes SchindelinFeb 20, 2007
  31. Simon 'corecode' SchubertFeb 20, 2007
  32. Johannes SchindelinFeb 18, 2007
  33. Junio C HamanoFeb 18, 2007
  34. Johannes SchindelinFeb 18, 2007
  35. Junio C HamanoFeb 18, 2007
  36. Johannes SchindelinFeb 18, 2007
  37. Junio C HamanoFeb 18, 2007
  38. Johannes SchindelinFeb 18, 2007
  39. Junio C HamanoFeb 18, 2007
  40. Johannes SchindelinFeb 18, 2007
  41. Jakub NarebskiFeb 18, 2007
  42. Johannes SchindelinFeb 18, 2007
  43. Junio C HamanoFeb 18, 2007
  44. Johannes SchindelinFeb 18, 2007
  45. Junio C HamanoFeb 18, 2007
  46. Johannes SchindelinFeb 18, 2007
  47. Junio C HamanoFeb 18, 2007
  48. Johannes SchindelinFeb 18, 2007
  49. Junio C HamanoFeb 18, 2007

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.