git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	Harry Jeffery <harry@exec64.co.uk>,
	git@vger.kernel.org
Subject: Re: git log --author=me
Date: Mon, 02 Nov 2015 19:24:16 +0100	[thread overview]
Message-ID: <vpqsi4oi7jj.fsf@anie.imag.fr> (raw)
In-Reply-To: <xmqqy4ege0p5.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Mon, 02 Nov 2015 10:05:42 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> 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.
>
> I do not think it would hurt too much to add "--mine" to look for
> "--author" that matches you, but on the other hand, I am not sure
> its value outweighs the additional noise in the manual page.

I have a few aliases to congratulate myself for being such an awesome
contributor from time to time ;-):

[alias]
	mymaster = log --oneline --author=Matthieu.Moy@imag.fr origin/master

It did require me to write these lines in my config file, but I think
that the trouble of writing them is smaller than the extra noise in the
manual page and possibly the output of `git log -h`. Having the
shorthand "--author=me" would be better than "git log --mine" as far as
cluttering the doc is concerned IMHO, but it's also likely to break
someone's search.

BTW, the output of `git log -h` is disappointing:

    $ git log -h
    usage: git log [<options>] [<revision-range>] [[--] <path>...]
       or: git show [<options>] <object>...
    
        -q, --quiet           suppress diff output
        --source              show source
        --use-mailmap         Use mail map file
        --decorate[=...]      decorate options
        -L <n,m:file>         Process line range n,m in file, counting from 1
    
There are far more options than this...

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2015-11-02 18:24 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 [this message]
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=vpqsi4oi7jj.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=harry@exec64.co.uk \
    --cc=schwab@linux-m68k.org \
    /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).