git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Victor Grishchenko <victor.grishchenko@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git and Linux tarball size evolution
Date: Sat, 10 Apr 2010 13:31:48 +0200	[thread overview]
Message-ID: <h2u81b0412b1004100431o8c543d4di7b6489211d053c98@mail.gmail.com> (raw)
In-Reply-To: <r2l1454bf6f1004090933g4e58277dh51c731ca6b097a45@mail.gmail.com>

On Fri, Apr 9, 2010 at 18:33, Victor Grishchenko
<victor.grishchenko@gmail.com> wrote:
> http://bouillon.math.usu.ru/files/linux-tarball-evol.png
>
> I plotted sizes of official linux kernel tarballs found at
> ftp://ftp.kernel.org against their dates. (Yep, the methodology is
> extremely dirty.)

Could you try using the sizes of *unpacked* tarballs?
gzip/bzip2 will offset the real growth a bit (maybe even a big bit).

> It is clear that git has changed the release pattern. But was it the
> reason why the development (and tarball size) returned to accelerated
> growth? Another possible interpretation is that 2.5->2.6 stage
> involved too much of reengineering, so "normal" incremental
> development slowed down for a while.

There were a lot of cleaning up in 2.5/2.6.

> Do git developers have any opinion on that?

The was Bitkeeper before Git, but also the development process
has changed, with Linus becoming less of nexus of it. He does
more merges than ever now, with a large part of integration and
testing done by subsystem maintainers and people like Andrew
Morton.
Besides, you cannot ignore the developments outside of Linux
world, which percipitate into kernel (things like new architectures).

      reply	other threads:[~2010-04-10 11:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 16:33 Git and Linux tarball size evolution Victor Grishchenko
2010-04-10 11:31 ` Alex Riesen [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

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

  git send-email \
    --in-reply-to=h2u81b0412b1004100431o8c543d4di7b6489211d053c98@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=victor.grishchenko@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).