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

Re: [RFC/PATCH] add diff-pairs tool

From
Jeff King <peff@peff.net>
Date
Dec 1, 2016, 21:30 UTC
Message-ID
<20161201213019.qfkqd324ommikym2@sigill.intra.peff.net>
In-Reply-To
<xmqq7f7j8iz6.fsf@gitster.mtv.corp.google.com>
On Thu, Dec 01, 2016 at 12:58:21PM -0800, Junio C Hamano wrote:
Show 21 quoted lines
> Jeff King <peff@peff.net> writes:
> 
> > On Thu, Dec 01, 2016 at 12:52:05PM -0800, Junio C Hamano wrote:
> >
> >> Jeff King <peff@peff.net> writes:
> >> 
> >> > This takes the output of `diff-tree -z --raw` and feeds it
> >> > back to the later stages of the diff machinery to produce
> >> > diffs in other formats.
> >> 
> >> A full circle.  This reminds me of the experiment done more than 10
> >> years ago at the beginning of the "diffcore transformations" design.
> >
> > Heh, I didn't even think to dig for prior art on the list.
> 
> It took me a while to dig it up because the topic is so old, but
> 
> https://public-inbox.org/git/Pine.LNX.4.58.0504251832480.18901@ppc970.osdl.org/
> 
> is the thread I had in mind.  The idea of rename detection followed
> soon afterwards.

Thanks for an interesting read. Your diff-tree-helper patch is very similar to what I wrote.

I do think the right decision was made back then. The single-process model is much more efficient, and it was over 10 years until somebody actually wanted to expose the functionality to a script (and even now, I'm not convinced enough people want it to even merit inclusion).

-Peff
Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 8 in “add diff-pairs tool”
  1. add diff-pairs toolJeff King, Dec 1, 2016
  2. Junio C HamanoDec 1, 2016
  3. Jeff KingDec 1, 2016
  4. Junio C HamanoDec 1, 2016
  5. Junio C HamanoDec 1, 2016
  6. Jeff KingDec 1, 2016
  7. Junio C HamanoDec 1, 2016
  8. Jeff KingDec 1, 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.