From: Junio C Hamano <gitster@pobox.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH next resend] bash completion: refactor diff options
Date: Sat, 17 Jan 2009 23:18:27 -0800 [thread overview]
Message-ID: <7vtz7xytdo.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1232240603-11729-1-git-send-email-trast@student.ethz.ch> (Thomas Rast's message of "Sun, 18 Jan 2009 02:03:23 +0100")
Thomas Rast <trast@student.ethz.ch> writes:
> diff, log and show all take the same diff options. Refactor them from
> __git_diff and __git_log into a variable, and complete them in
> __git_show too.
>
> Signed-off-by: Thomas Rast <trast@student.ethz.ch>
>
> ---
>
> Any news on this?
> +__git_diff_common_options="--stat --numstat --shortstat --summary
> --patch-with-stat --name-only --name-status --color
> --no-color --color-words --no-renames --check
> --full-index --binary --abbrev --diff-filter=
> - --find-copies-harder --pickaxe-all --pickaxe-regex
> + --find-copies-harder
The changes around pickaxe made me "Huh?". For log pickaxe makes very
good sense but for a single diff it doesn't, yet the original seems to
have had them only on "git diff" and not on "git log", which feels wrong.
Other than that, I think the patch tries to achieve a great thing in the
longer term---we do not have to worry about common parts going out of sync
between diff and log family of commands.
next prev parent reply other threads:[~2009-01-18 7:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 13:14 [PATCH] bash completion: refactor diff options Thomas Rast
2009-01-12 9:16 ` [PATCH next] " Thomas Rast
2009-01-18 1:03 ` [PATCH next resend] " Thomas Rast
2009-01-18 7:18 ` Junio C Hamano [this message]
2009-01-19 17:31 ` Shawn O. Pearce
2009-01-19 21:17 ` [PATCH v2 1/2] bash completion: move pickaxe options to log Thomas Rast
2009-01-19 21:18 ` [PATCH v2 2/2] bash completion: refactor diff options Thomas Rast
2009-01-20 8:36 ` 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=7vtz7xytdo.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=trast@student.ethz.ch \
/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).