From: Alexei Sholik <alcosholik@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH 2/2] Add Author and Documentation sections to git-for-each-ref.txt
Date: Wed, 9 Mar 2011 14:14:10 +0200 [thread overview]
Message-ID: <AANLkTimyW7CMSkXndHOW9Gbvu124YYT5e-SdGUq3-OGu@mail.gmail.com> (raw)
In-Reply-To: <4D773570.4010803@drmicha.warpmail.net>
On 9 March 2011 10:08, Michael J Gruber <git@drmicha.warpmail.net> wrote:
> +Evangelisation
> ---------------
> Jeff King <peff@peff.net>
>
> Just kidding!
>
> (Jeff is the 2nd main f-e-r author, but Junio created it.)
>
> Michael ;)
>
I meant no offense. Just ran this command
git blame -p "$1" | awk '$1 ~ /author$/ { print substr($0,
length("author "), length($0)) }' | sort | uniq -c | sort -nr
on the for-each-ref.c and saw that Junio had the first place by a
relatively large margin.
Similarly, the git-for-each-ref.txt (I used plain git blame on this
one) has mostly been composed by Junio. Surely, it's not my privilege
to decide on the list of authors, but I wonder why the original
authors haven't claimed their rightful place in the docs.
--
Best regards,
Alexei Sholik
next prev parent reply other threads:[~2011-03-09 12:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 13:16 [PATCH 0/2] A couple of tweaks in git-for-each-ref.txt Alexei Sholik
2011-03-08 13:16 ` [PATCH 1/2] Documentation: remove redundant colons " Alexei Sholik
2011-03-09 7:55 ` Michael J Gruber
2011-03-08 13:16 ` [PATCH 2/2] Add Author and Documentation sections to git-for-each-ref.txt Alexei Sholik
2011-03-09 8:08 ` Michael J Gruber
2011-03-09 12:14 ` Alexei Sholik [this message]
2011-03-17 14:20 ` Will Palmer
2011-03-17 19:34 ` Jeff King
2011-03-17 19:51 ` Alexei Sholik
2011-03-17 19:54 ` Jeff King
2011-03-17 20:10 ` Alexei Sholik
2011-03-09 20:17 ` Junio C Hamano
2011-03-10 22:37 ` Jeff King
2011-03-10 23:09 ` Junio C Hamano
2011-03-11 6:20 ` Jeff King
2011-03-11 8:09 ` Junio C Hamano
2011-03-12 9:52 ` Alexei Sholik
2011-03-13 3:02 ` Jeff King
2011-03-13 6:34 ` Junio C Hamano
2011-03-13 6:47 ` Jeff King
2011-03-13 7:33 ` Junio C Hamano
2011-03-13 13:27 ` Michael J Gruber
2011-03-17 6:59 ` Jeff King
2011-03-09 19:54 ` [PATCH 0/2] A couple of tweaks in git-for-each-ref.txt 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=AANLkTimyW7CMSkXndHOW9Gbvu124YYT5e-SdGUq3-OGu@mail.gmail.com \
--to=alcosholik@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).