From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: Some stats for 1.6.6
Date: Thu, 24 Dec 2009 11:43:44 -0800 [thread overview]
Message-ID: <20091224194344.GA15212@spearce.org> (raw)
In-Reply-To: <7v637wjlor.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> Here is a contributor statistics.
>
> release new this total date
> v0.99 47 47 47 2005-07-10
...
> v1.6.5 27 101 693 2009-10-10
> v1.6.6 17 99 710 2009-12-23
>
> During the entire history leading to 1.6.6, 710 authors contributed code
> and documentation. The changes since 1.6.5 were made by 99 authors, among
> which 17 are the new contributors to the project.
This is what impresses me most about Git.
Its not our simple on disk format, or our network protocols, or how
well we have been able to avoid breaking things. Its our community.
Almost 100 people contributed code into the most recent release,
and in just the last 6 months we picked up 44 new contributors.
I wish all open source projects ran this well.
> Let's thank and welcome them to the community(sorted LC_ALL=C): Andrew
> Myrick, Brian Collins, Carlos R. Mafra, Dan Zwell, Erick Mattos, Gisle
> Aas, Guillermo S. Romero, Jean Privat, Jimmy Angelakos, Jindrich
> Makovicka, Mizar, Nasser Grainawi, Pauli Virtanen, Raman Gupta, Robert
> Zeh, Tim Henigan, and Vietor Liu.
Welcome! But more importantly, thank you for making Git better!
:-)
--
Shawn.
next prev parent reply other threads:[~2009-12-24 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 1:06 [ANNOUNCE] Git 1.6.6 Junio C Hamano
2009-12-24 18:01 ` Some stats for 1.6.6 Junio C Hamano
2009-12-24 19:43 ` Shawn O. Pearce [this message]
2009-12-25 0:25 ` Branch shuffling after 1.6.6 release plans Junio C Hamano
2009-12-25 11:30 ` Thomas Rast
2009-12-25 12:28 ` Ilari Liusvaara
2009-12-26 8:01 ` Jeff King
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=20091224194344.GA15212@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).