git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git and Linux tarball size evolution

From
Alex Riesen <raa.lkml@gmail.com>
Date
Apr 10, 2010, 11:31 UTC
Message-ID
<h2u81b0412b1004100431o8c543d4di7b6489211d053c98@mail.gmail.com>
In-Reply-To
<r2l1454bf6f1004090933g4e58277dh51c731ca6b097a45@mail.gmail.com>

On Fri, Apr 9, 2010 at 18:33, Victor Grishchenko <victor.grishchenko@gmail.com> wrote:

Show 5 quoted lines
> 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).

Show 5 quoted lines
> 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).

Previous: Victor Grishchenko
Message 2 of 2 in “Git and Linux tarball size evolution”
  1. Victor GrishchenkoApr 9, 2010
  2. Alex RiesenApr 10, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.