From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Missing documentation for GIT_DIFF_OPTS and GIT_EXTERNAL_DIFF
Date: Wed, 14 Feb 2007 02:27:50 +0100 [thread overview]
Message-ID: <eqtof8$8id$1@sea.gmane.org> (raw)
In-Reply-To: 20070213223657.GC4266@nan92-1-81-57-214-146.fbx.proxad.net
Yann Dirson wrote:
> I noticed today, after unsuccessfully trying GIT_DIFF_OPTS=-U2, that
> 1) it did not work, 2) the doc in 1.4.4.4 tells about using
> "GIT_DIFF_OPTS=-c", which does not work either and 3) there is
> virtually no more doc about it in HEAD.
>
> It would be useful to document which flags are recognized, and notably
> that -u<n> has to be used instead of GNU diff's -U<n>.
>
> At the same time, I noticed that GIT_EXTERNAL_DIFF is not described in
> the diff docs either, although it is described in the main git.txt
> page (which may not be the place where users would look for it - at
> least, only my grep aiming to be accurate before composing this mail
> finally found it).
GIT_DIFF_OPTS are also described there.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-02-14 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 22:36 Missing documentation for GIT_DIFF_OPTS and GIT_EXTERNAL_DIFF Yann Dirson
2007-02-14 1:27 ` Jakub Narebski [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='eqtof8$8id$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).