From: Junio C Hamano <gitster@pobox.com>
To: Scott Chacon <schacon@gmail.com>
Cc: git@vger.kernel.org, Kjetil Barvik <barvik@broadpark.no>
Subject: Re: [PATCH 0/2] git checkout: one bugfix and one cosmetic change
Date: Sun, 15 Mar 2009 12:38:55 -0700 [thread overview]
Message-ID: <7viqma7f00.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vab7m8x5w.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 15 Mar 2009 11:21:15 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Kjetil Barvik <barvik@broadpark.no> writes:
>
>> Just one small bugfix patch, and one small cosmetic change.
>>
>> By the way, I wonder how often the list of 'Primary Authors' and
>> 'Contributors' on the webpage http://git-scm.com/about is updated.
>> Should'nt it be updated when a new release, like v1.6.2, is made?
>
> Thanks for noticing. Though git-scm.com is not under my control, the site
> is considered the official git homepage these days, and I am glad to see
> improvements to its contents discussed here. I do not see Scott very
> often on this list these days, so I am CC'ing him.
Ragarding the list on the page, I have one thought (not complete enough to
be called suggestion) and one datapoint:
(1) The boundary between the "Primary Authors" vs "Contributors" seems to
be set at 50 commits with the current table. This would mean that we
will have a lot more primary authors as project progresses. Is this
desirable?
We have 14999 non-merge commits as of 1.6.2; perhaps a per-cent (or a
half per-cent) cutoff rule would give a more balanced and consistent
view in the longer term [*1*]?
(2) This script:
$ git shortlog -s v1.6.1 | sed -e 's/^[ 0-9]*//' >/var/tmp/1
$ git shortlog -s v1.6.2 | sed -e 's/^[ 0-9]*//' >/var/tmp/2
$ comm -13 /var/tmp/[12]
produces the list of new contributors. There are 39 names [*2*].
[Footnotes]
*1* A more drastic change would be not to have two lists, but just one.
*2* Thanks and welcome.
Allan Caffee, Ben Walton, Benjamin Kramer, Benjamin Sergeant, Benoit
Sigoure, Danijel Tasov, David J. Mellor, Devin Doucette, Dévai Tamás,
Elijah Newren, Eric Kidd, Fabian Franz, Felipe Contreras, Geoffrey
Thomas, Henrik Austad, Jacob Helwig, Jake Goulding, Jeremy White,
Johannes Gilger, Jonas Flodén, Keith Cascio, Kjetil Barvik, Marc
Branchaud, Marc-Andre Lureau, Nazri Ramliy, Pat Notz, Paul Jarc, Peter
Oberndorfer, Ray Chuan, Roy Lee, Serge van den Boom, Sergei Organov,
Stefan Karpinski, Tay Ray Chuan, Ted Pavlic, Tor Arne Vestbø, Vitaly
"_Vi" Shukela, Väinö Järvelä, jidanni@jidanni.org.
next prev parent reply other threads:[~2009-03-15 19:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 11:38 [PATCH 0/2] git checkout: one bugfix and one cosmetic change Kjetil Barvik
2009-03-15 11:38 ` [PATCH 1/2] checkout bugfix: use stat.mtime instead of stat.ctime in two places Kjetil Barvik
2009-03-15 11:38 ` [PATCH 2/2] make the ST_{C,M}TIME_NSEC macros more function like Kjetil Barvik
2009-03-15 20:01 ` Junio C Hamano
2009-03-15 21:59 ` Kjetil Barvik
2009-03-16 7:12 ` Junio C Hamano
2009-03-17 17:38 ` Kjetil Barvik
2009-03-15 18:21 ` [PATCH 0/2] git checkout: one bugfix and one cosmetic change Junio C Hamano
2009-03-15 19:38 ` Junio C Hamano [this message]
2009-03-16 16:12 ` Michael J Gruber
2009-03-17 4:56 ` Kris Shannon
2009-03-17 8:43 ` Jeff King
2009-03-17 13:39 ` Michael J Gruber
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=7viqma7f00.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barvik@broadpark.no \
--cc=git@vger.kernel.org \
--cc=schacon@gmail.com \
/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).