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

Re: [RFC 1/4] Add diff-diff, which compares the diffs of two commits

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 15, 2007, 19:34 UTC
Message-ID
<7vzlwblpk6.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1197737505128-git-send-email-prohaska@zib.de>
Steffen Prohaska <prohaska@zib.de> writes:
Show 7 quoted lines
> At this point, I'm only seeking comments about the general direction.
> The patches should not be applied to git.git.
>
>  - Do you think something like this would be helpful?
>  - Are similar approaches already available?
>  - How do you use git to support code review; besides discussing
>    patches on mailing lists?

I think there are other good building blocks you can use outside git to help reviewing evolution of patches (interdiff comes to mind).

When I receive a replacement series to a topic, I use RP script (available in my 'todo' branch and checked out in Meta/ directory in my work area, together with other scripts from 'todo'), which:

 * finds where the older series were applied;
 * detaches HEAD at that commit, and apply the new series;
 * runs diff between the old and new;
 * updates the tip of that topic with the new series.

After it finishes, "diff topic@{1} topic" becomes the incremental diff between the old and the new series, and if I do not like the end result, I can reset --hard back to topic@{1}.

Previous: Steffen Prohaska
Message 8 of 8 in “[RFC 1/4] Add diff-diff, which compares the diffs of two commits”
  1. Steffen ProhaskaDec 15, 2007
  2. 2/4 gitk: Add diff-diff supportSteffen Prohaska, Dec 15, 2007
  3. 3/4 gitk: Refactor getblobdiffline to split off adddifflineSteffen Prohaska, Dec 15, 2007
  4. 4/4 gitk: Use adddiffline to nicely format diff-diffSteffen Prohaska, Dec 15, 2007
  5. Johannes SchindelinDec 15, 2007
  6. Björn SteinbrinkDec 15, 2007
  7. Steffen ProhaskaDec 15, 2007
  8. Junio C HamanoDec 15, 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.