public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Michael J Gruber <git@drmicha•warpmail.net>
Cc: Duy Nguyen <pclouds@gmail•com>,
	Harry Jeffery <harry@exec64•co.uk>,
	Git Mailing List <git@vger•kernel.org>
Subject: Re: git log --author=me
Date: Tue, 03 Nov 2015 13:30:50 -0800	[thread overview]
Message-ID: <xmqq1tc6db3p.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <56388BEC.7050207@drmicha.warpmail.net> (Michael J. Gruber's message of "Tue, 3 Nov 2015 11:26:52 +0100")

Michael J Gruber <git@drmicha•warpmail.net> writes:

> Alternatively: How about teaching git-completion to complete the
> argument to --author? Expensive, I know, but faster than typing it out
> or realising "Michael J" is not as unique as you think ;)

Or

    $ git log --author="$me"

with

    me='Michael J Gruber <git@drmicha•warpmail.net>'

in your $HOME/.profile or somewhere?

I personally would find "--author=me" not so bad (especially if
finding _my_ work were a very important workflow element), and I may
even tell people to do

    $ git log --author='[m]e'

if they want to find anybody with substring 'me' in their ident.

But that is only if it weren't for existing users, and we live in an
imperfect world where we seem to have many of existing users
already.

      reply	other threads:[~2015-11-03 21:31 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
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 [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=xmqq1tc6db3p.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@drmicha$(echo .)warpmail.net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=harry@exec64$(echo .)co.uk \
    --cc=pclouds@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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