From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] bash: gitk accepts common log-shortlog options
Date: Wed, 22 Jul 2009 09:05:05 -0500 [thread overview]
Message-ID: <20090722140505.GQ3581@saturnine> (raw)
In-Reply-To: <200907220036.42917.trast@student.ethz.ch>
On Wed, Jul 22, 2009 at 12:36:36AM +0200, Thomas Rast wrote:
> SZEDER Gábor wrote:
> > Commit a393777e (bash completion: refactor common log, shortlog and gitk
> > options, 2009-02-16) introduced a list of command line options that go
> > well with 'git log' and 'git shortlog' but not with gitk. However,
> > these options are all 'git rev-list' options, and, therefore, are
> > accepted by gitk, too.
> [...]
> > + --author= --committer= --grep=
> > + --all-match
>
> At the time, I tried to skip options to gitk that disconnect history
> in places where it really is connected. This applies to --author,
> --committer and --grep, which also have a GUI equivalent. However,
> --all-match doesn't, and then the other three are also needed, so I
> guess this makes sense.
I see. I was not sure what you meant by "go well", but suspected
this. However, the '--no-merges' option was already there earlier,
and it also produces disconnected history. I'm not sure how often
these options are used with gitk, but it just happened yesterday that
I wanted to use 'gitk --author=<me> ...' to find one of my commits.
Best,
Gábor
prev parent reply other threads:[~2009-07-22 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 22:20 [PATCH] bash: gitk accepts common log-shortlog options SZEDER Gábor
2009-07-21 22:36 ` Thomas Rast
2009-07-22 14:05 ` SZEDER Gábor [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=20090722140505.GQ3581@saturnine \
--to=szeder@ira.uka.de \
--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