From: Junio C Hamano <gitster@pobox.com>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] diff: added '-q' option, short option for '--quiet'
Date: Wed, 14 Jan 2015 10:52:52 -0800 [thread overview]
Message-ID: <xmqqegqx9ou3.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1421256901-30560-1-git-send-email-kuleshovmail@gmail.com> (Alexander Kuleshov's message of "Wed, 14 Jan 2015 23:35:01 +0600")
Alexander Kuleshov <kuleshovmail@gmail.com> writes:
> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
> ---
> Documentation/diff-options.txt | 1 +
> diff.c | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
I think we have deliberately refrained from doing this, as it will
make "git diff" inconsistent with the underlying "git diff-fiels".
>
> diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt
> index 2b15050..9160c90 100644
> --- a/Documentation/diff-options.txt
> +++ b/Documentation/diff-options.txt
> @@ -491,6 +491,7 @@ ifndef::git-log[]
> That is, it exits with 1 if there were differences and
> 0 means no differences.
>
> +-q
> --quiet::
> Disable all output of the program. Implies `--exit-code`.
> endif::git-log[]
> diff --git a/diff.c b/diff.c
> index 6ad8970..d778df7 100644
> --- a/diff.c
> +++ b/diff.c
> @@ -3798,7 +3798,7 @@ int diff_opt_parse(struct diff_options *options, const char **av, int ac)
> }
> else if (!strcmp(arg, "--exit-code"))
> DIFF_OPT_SET(options, EXIT_WITH_STATUS);
> - else if (!strcmp(arg, "--quiet"))
> + else if (!strcmp(arg, "--quiet") || !strcmp(arg, "-q"))
> DIFF_OPT_SET(options, QUICK);
> else if (!strcmp(arg, "--ext-diff"))
> DIFF_OPT_SET(options, ALLOW_EXTERNAL);
prev parent reply other threads:[~2015-01-14 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 17:35 [PATCH] diff: added '-q' option, short option for '--quiet' Alexander Kuleshov
2015-01-14 18:52 ` Junio C Hamano [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=xmqqegqx9ou3.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kuleshovmail@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.