From: Andreas Schwab <schwab@linux-m68k.org>
To: Harry Jeffery <harry@exec64.co.uk>
Cc: git@vger.kernel.org
Subject: Re: git log --author=me
Date: Mon, 02 Nov 2015 18:50:38 +0100 [thread overview]
Message-ID: <8737wos32p.fsf@igel.home> (raw)
In-Reply-To: <563764B8.4010101@exec64.co.uk> (Harry Jeffery's message of "Mon, 2 Nov 2015 13:27:20 +0000")
Harry Jeffery <harry@exec64.co.uk> writes:
> The purpose being to make finding your own commits quicker and easier:
> git log --author=me
Since --author does a regexp search, this would most likely break
someone's searches. Better add a new option for that functionality.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2015-11-02 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 13:27 git log --author=me Harry Jeffery
2015-11-02 17:50 ` Andreas Schwab [this message]
2015-11-02 18:05 ` Junio C Hamano
2015-11-02 18:24 ` Matthieu Moy
2015-11-02 18:37 ` Duy Nguyen
2015-11-03 10:26 ` Michael J Gruber
2015-11-03 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=8737wos32p.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=harry@exec64.co.uk \
/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).