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

Re: [PATCH] diff --no-index: support more than one file pair

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Jan 12, 2012, 17:40 UTC
Message-ID
<CACsJy8B460CwtACV+o0wnwqi1On_oEavLfDAL8f=w6kyfktKcQ@mail.gmail.com>
In-Reply-To
<vpqmx9te08z.fsf@bauges.imag.fr>

On Thu, Jan 12, 2012 at 4:30 PM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:

Show 5 quoted lines
>>  - might be easier to script (just throw them all to xargs)
>
> I don't see a use-case where a command produces old1 new1 old2 new2, but
> if there is one, then "| xargs -n 2 diff" is the solution. You don't
> need your patch.
Unthorough thought. I agree with you.
Show 6 quoted lines
>>  - hell, i might even benefit from git copy/modify detection
>
> I don't see how, if you specify explicitely the pairs (old, new). You
> may have such benefit if you let the command-line express "here's a
> bunch of old files, and a bunch of new ones", but not with your proposed
> syntax.

That's what git gives to diff machinery: a set of file pairs, and the diff machinery has to figure out copy/modify pairs, shuffling them up if necessary. I simply cut of tree traversal part out and feed file pairs directly to diff machinery. I remember long long time ago Junio asked for assistance about code moving support within a file. It has not come up (at least in public), but one can hope it'll come someday.

-- 
Duy
Previous: Matthieu MoyNext: Matthieu Moy
Message 5 of 7 in “diff --no-index: support more than one file pair”
  1. diff --no-index: support more than one file pairNguyễn Thái Ngọc Duy, Jan 12, 2012
  2. Matthieu MoyJan 12, 2012
  3. Nguyen Thai Ngoc DuyJan 12, 2012
  4. Matthieu MoyJan 12, 2012
  5. Nguyen Thai Ngoc DuyJan 12, 2012
  6. Matthieu MoyJan 12, 2012
  7. Neal KreitzingerJan 12, 2012

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.