git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Junio Hamano <gitster@pobox.com>
Subject: Re: Git Chronicles, updated?
Date: Thu, 08 Jul 2010 06:31:10 -0700	[thread overview]
Message-ID: <7viq4qqew1.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <201007081057.51946.jnareb@gmail.com> (Jakub Narebski's message of "Thu\, 8 Jul 2010 10\:57\:48 +0200")

Jakub Narebski <jnareb@gmail.com> writes:

> Now that's Git Together '10 comes near, I wonder if it would be possible
> to have updated "Git Chronicles".  It was two years of development ago.
> Hopefuly Junio still has tools he used to generate data for this talk.

The tools are unfortunately very small parts of the story.

> One of graphs shown was growth of git codebase and of git contributors.
> Did git development stabilized during those two years since 2008, or
> does it still reads as active rather than stable development?
>
> Another interesting graphs was plot showing number of surviving lines 
> added in a give release relative to mumber of all lines added in said 
> release.  This was used to detect which releases were important ones.
> Were there any releases between 2008 and 2010 of significant importance?

These two are both interesting questions to ask, and luckily they are
mostly mechanical.  I'll try to dig up the tools to help generate them.

> The slides for "Git Chronicles" from 2008 closed with timelines of git 
> features.  Were there any important user-visible features added since 
> 2008 (notes, sparse checkout, "smart" HTTP)?

This was produced manually, out of release notes, blame output from the
Documentation/, as "feature dates" cannot be discerned mechanically
(e.g. history of "blame annotate shootout" needs to be written by somebody
who can tell that the current "git blame" came from "git pickaxe"
experiment, and all three variants were written from the general algorithm
description without code I wrote a long time ago).

> What might be also interesting is a descriotpion of how some important 
> feature came into being, with hint of an idea, discussions, prototypes, 
> failed starts, dropped patches, reworkings, accepted version and then
> improvements.  If one is not watching git mailing list regularly for a 
> longer time, what one sees is the final product.  One doesn't know what 
> it might to take to get a large feature into git...

Yes, it would be very interesting.  Will you volunteer to be one of the
git chroniclers?  It was a lot of work back then, and I don't think I can
do this properly as a two-day hack-job by myself.

      reply	other threads:[~2010-07-08 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08  8:57 Git Chronicles, updated? Jakub Narebski
2010-07-08 13:31 ` Junio C Hamano [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7viq4qqew1.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).