From: Martin Vaeth <martin@mvath.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Bug #565566: Why is it still not fixed?
Date: Fri, 26 Feb 2016 12:59:26 +0000 (UTC) [thread overview]
Message-ID: <napi7e$47u$1@ger.gmane.org> (raw)
In-Reply-To: CAGfcS_n-vD0NgrqzqvGhCt3y0E2OkipvvBmu1eh8gUoe+_jGgw@mail.gmail.com
Rich Freeman <rich0@gentoo.org> wrote:
>>
>> And currently the git history is still almost empty...
>>
>
> If you want pre-migration history you need to fetch that separately.
How? Neither on gitweb.gentoo.org nor on github I found an obvious
repository with this data.
> It is about 1.7G.
> Considering that this represents a LOT more than 2-3 years of history
If the 1.7G are fully compressed history, this would confirm
my estimate rather precisely, if it represents (1700/120 - 1) ~ 13 years.
Gentoo exists since 2002, so it seems my estimate was very good.
> (including periods where the commit rate was higher than it is today)
One of my assumptions for the estimate was that this rate is
constant in the average. Also I am not sure whether you right
that this rate was really higher, previously: Nowadays, even a
rather trivial eclass-update is separated into several commits,
increasing the amount of data needed for storage.
> I think your estimates of where the migrated repo will be in 2-3 years
> is too high.
Note that I compared squashfs with a git user who does not even
care about git-internal recompression. Of course, you can decrease
the factor somewhat if e.g. your checked-out tree is still stored
on squashfs. This does not change the fact that the factor will
increase every year by about 1 (or probably more, because git
uses the uneffective gzip compression, only).
next prev parent reply other threads:[~2016-02-26 12:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 17:14 [gentoo-dev] Bug #565566: Why is it still not fixed? Patrick Lauer
2016-02-23 18:07 ` Alec Warner
2016-02-23 21:53 ` Patrick Lauer
2016-02-24 0:33 ` [gentoo-dev] " Duncan
2016-02-24 0:50 ` Kristian Fiskerstrand
2016-02-24 2:53 ` Rich Freeman
2016-02-24 4:24 ` Duncan
2016-02-24 5:49 ` Kent Fredric
2016-02-24 7:29 ` Duncan
2016-02-24 10:35 ` Kent Fredric
2016-02-24 19:18 ` Raymond Jennings
2016-02-24 20:16 ` Luis Ressel
2016-02-24 21:15 ` Daniel Campbell
2016-02-24 22:16 ` Brian Dolbec
2016-02-25 7:12 ` Martin Vaeth
2016-02-25 23:12 ` Gordon Pettey
2016-02-26 11:00 ` Martin Vaeth
2016-02-26 11:11 ` Rich Freeman
2016-02-26 12:59 ` Martin Vaeth [this message]
2016-02-26 13:37 ` Rich Freeman
2016-02-27 10:30 ` Martin Vaeth
2016-02-25 5:03 ` Duncan
2016-02-25 5:46 ` Kent Fredric
2016-02-25 8:02 ` Consus
2016-02-25 8:59 ` Kent Fredric
2016-02-25 10:48 ` M. J. Everitt
2016-02-24 4:38 ` Vadim A. Misbakh-Soloviov
2016-02-24 5:36 ` Duncan
2016-02-24 2:39 ` Rich Freeman
2016-02-27 13:14 ` Luca Barbato
2016-02-27 22:35 ` Raymond Jennings
2016-02-27 22:50 ` Robin H. Johnson
2016-02-27 23:08 ` Patrick Lauer
2016-02-28 8:27 ` Martin Vaeth
2016-02-28 3:28 ` Duncan
2016-02-23 18:46 ` [gentoo-dev] " Alexis Ballier
2016-02-23 21:54 ` Patrick Lauer
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='napi7e$47u$1@ger.gmane.org' \
--to=martin@mvath.de \
--cc=gentoo-dev@lists.gentoo.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