From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] diff --no-index: support more than one file pair
Date: Thu, 12 Jan 2012 10:37:37 -0600 [thread overview]
Message-ID: <4F0F0C51.3050706@gmail.com> (raw)
In-Reply-To: <1326359371-13528-1-git-send-email-pclouds@gmail.com>
On 1/12/2012 3:09 AM, Nguyễn Thái Ngọc Duy wrote:
> This allows you to do
>
> git diff --no-index file1.old file1.new file2.old file2.new...
>
> It could be seen as an abuse of "git --no-index", but it's very
> tempting considering many bells and whistles git's diff machinery
> provides.
>
I see that git-diff can be used in place of linux diff for totally
untracked file pairs (which is kind of neat, I guess, if you're partial
to git like I am and would probably prefer to use it as your primary
file-system interface if you could). I assume this new syntax implies
manual usage since scripting this input is less straightforward than
iterating thru a single pair via xargs, etc. In that context, I also
see that git-difftool doesn't bring up kdiff3 (or whatever) but just
does a text diff (git 1.7.1) which is mildly disappointing for mere
mortals like myself who prefer to read side-by-side gui diffs over text
diffS. This, of course, is also preference for someone like me who
wouldn't mind prefixing all of my commands with "git " ;-)
v/r,
neal
prev parent reply other threads:[~2012-01-12 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 9:09 [PATCH] diff --no-index: support more than one file pair Nguyễn Thái Ngọc Duy
2012-01-12 9:14 ` Matthieu Moy
2012-01-12 9:17 ` Nguyen Thai Ngoc Duy
2012-01-12 9:30 ` Matthieu Moy
2012-01-12 17:40 ` Nguyen Thai Ngoc Duy
2012-01-12 18:26 ` Matthieu Moy
2012-01-12 16:37 ` Neal Kreitzinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0F0C51.3050706@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.