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

Re: [RFC/PATCH 0/2] git diff <(command1) <(command2)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 16, 2016, 09:50 UTC
Message-ID
<alpine.DEB.2.20.1611161039590.3746@virtualbox>
In-Reply-To
<xmqqtwb9wywp.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Mon, 14 Nov 2016, Junio C Hamano wrote:
Show 5 quoted lines
> I _think_ the no-index mode was primarily for those who want to use
> our diff as a replacement for GNU and other diffs, and from that
> point of view, I'd favour not doing the "comparing symbolic link?
> We'll show the difference between the link contents, not target"
> under no-index mode myself.

If I read this correctly, then we are in agreement that the default for --no-index should be as it is right now, i.e. comparing symlink targets as opposed to --follow-links.

> That is a lot closer to the diff other people implemented, not ours.
> Hence the knee-jerk reaction I gave in
> 
> http://public-inbox.org/git/xmqqinrt1zcx.fsf@gitster.mtv.corp.google.com
Let me quote the knee-jerk reaction:
> My knee-jerk reaction is:
>
>  * The --no-index mode should default to your --follow-symlinks
>    behaviour, without any option to turn it on or off.
But this is the exact opposite of what I find reasonable.

Ciao, Johannes

Previous: Junio C HamanoNext: Junio C Hamano
Message 13 of 18 in “git diff <(command1) <(command2)”
  1. 0/2 git diff <(command1) <(command2)Dennis Kaarsemaker, Nov 11, 2016
  2. 2/2 diff --no-index: support reading from pipesDennis Kaarsemaker, Nov 11, 2016
  3. 1/2 diff --no-index: add option to follow symlinksDennis Kaarsemaker, Nov 11, 2016
  4. Junio C HamanoNov 11, 2016
  5. Jacob KellerNov 11, 2016
  6. Johannes SchindelinNov 12, 2016
  7. Junio C HamanoNov 14, 2016
  8. Michael J GruberNov 14, 2016
  9. Johannes SchindelinNov 14, 2016
  10. Junio C HamanoNov 14, 2016
  11. Michael J GruberNov 14, 2016
  12. Junio C HamanoNov 14, 2016
  13. Johannes SchindelinNov 16, 2016
  14. Junio C HamanoNov 16, 2016
  15. Junio C HamanoNov 16, 2016
  16. Dennis KaarsemakerNov 12, 2016
  17. Jeff KingNov 12, 2016
  18. Jacob KellerNov 11, 2016

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.