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
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Jan 12, 2012, 09:30 UTC
Message-ID
<vpqmx9te08z.fsf@bauges.imag.fr>
In-Reply-To
<CACsJy8BvA_o1+xrOx4hYhmwNWpsRnh5+mftb471h3yFW2b6vhA@mail.gmail.com>
Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
> Single operation has its advantages:
>
>  - one pager
>  - one stat and summary

I buy these, and I understand why they apply to "git diff" and not GNU diff.

>  - 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.

>  - 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.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Nguyen Thai Ngoc DuyNext: Nguyen Thai Ngoc Duy
Message 4 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.