From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Some stats for 1.6.6
Date: Thu, 24 Dec 2009 10:01:24 -0800 [thread overview]
Message-ID: <7v637wjlor.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 7vpr65kwnt.fsf@alter.siamese.dyndns.org
Now 1.6.6 is out, the next one will be 1.7.0 that hopefully will happen
sometime late in February 2010. I wish people happy holidays, and expect
them to slow down (I would ;-) for the remainder of the year.
Here are a few sets of numbers to help relax your mind away from hacking.
The very initial release of "git" consisted of 11 files, 1244 lines in
total, all written by Linus. Here is the result of a "reverse-blame" that
counts how much of that original version still can be found in the latest
version:
surviving original path (survival%)
16 40 Makefile (40.00%)
16 168 README (9.52%)
54 93 cache.h (58.06%)
4 23 cat-file.c (17.39%)
6 172 commit-tree.c (3.48%)
4 51 init-db.c (7.84%)
99 259 read-cache.c (38.22%)
0 43 read-tree.c (0.00%)
7 81 show-diff.c (8.64%)
39 248 update-cache.c (15.72%)
0 66 write-tree.c (0.00%)
245 1244 Total (19.69%)
As can be seen in "cache.h", the very basic data structures and accessor
methods haven't changed much. v0.99, which was the last version Linus
tagged before handing the development over to me, still retained 46% of
the original.
Here is a contributor statistics.
release new this total date
v0.99 47 47 47 2005-07-10
v1.0.0 68 89 115 2005-12-21
v1.1.0 4 19 119 2006-01-08
v1.2.0 8 32 127 2006-02-12
v1.3.0 22 56 149 2006-04-18
v1.4.0 18 57 167 2006-06-10
v1.4.1 3 30 170 2006-07-01
v1.4.2 13 47 183 2006-08-12
v1.4.3 9 43 192 2006-10-18
v1.4.4 8 42 200 2006-11-14
v1.5.0 25 72 225 2007-02-14
v1.5.1 14 59 239 2007-04-03
v1.5.2 19 70 258 2007-05-20
v1.5.3 53 126 311 2007-09-02
v1.5.4 82 163 393 2008-02-01
v1.5.5 33 112 426 2008-04-07
v1.5.6 46 114 472 2008-06-18
v1.6.0 40 105 512 2008-08-17
v1.6.1 49 147 561 2008-12-24
v1.6.2 34 109 595 2009-03-03
v1.6.3 45 117 640 2009-05-06
v1.6.4 26 98 666 2009-07-29
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.
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.
next prev parent reply other threads:[~2009-12-24 18:04 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 ` Junio C Hamano [this message]
2009-12-24 19:43 ` Some stats for 1.6.6 Shawn O. Pearce
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=7v637wjlor.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.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).