From: Thomas Rast <trast@student.ethz.ch>
To: git@vger.kernel.org
Cc: Junio C Hamano <junio@pobox.com>
Subject: Re: [RFC PATCH] diff --no-index: test for pager after option parsing
Date: Wed, 7 Jan 2009 01:09:03 +0100 [thread overview]
Message-ID: <200901070109.25579.trast@student.ethz.ch> (raw)
In-Reply-To: <1231286163-9422-1-git-send-email-trast@student.ethz.ch>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
Speaking of diff --no-index code, there's also this bit:
/* diff-no-index.c:206 */
for (i = 1; i < argc - 2; ) {
int j;
if (!strcmp(argv[i], "--no-index"))
i++;
else if (!strcmp(argv[1], "-q"))
options |= DIFF_SILENT_ON_REMOVED;
Note the argv[i] vs. argv[1]. The entire block is from 0569e9b ("git
diff": do not ignore index without --no-index, 2008-05-23).
While it seems obvious that this should be argv[i], I'm rather
confused by the option itself. It is not documented in my version of
git-diff(1). Furthermore, I can't see what being silent about removed
paths (which relates to the index?) has to do with a diff --no-index
(which takes two paths that must exist).
Or perhaps I should take the "no mails/patches after midnight" rule a
tad bit more serious...
--
Thomas Rast
trast@{inf,student}.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-07 0:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 23:56 [RFC PATCH] diff --no-index: test for pager after option parsing Thomas Rast
2009-01-07 0:09 ` Thomas Rast [this message]
2009-01-07 0:09 ` Junio C Hamano
2009-01-07 3:20 ` Miklos Vajna
2009-01-07 6:42 ` Jeff King
2009-01-07 7:02 ` Junio C Hamano
2009-01-07 11:15 ` [PATCH] diff --no-index -q: fix endless loop Thomas Rast
2009-01-07 21:30 ` Junio C Hamano
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=200901070109.25579.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=junio@pobox.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 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).