Gentoo Archives: gentoo-scm

From: Rich Freeman <rich0@g.o>
To: gentoo-scm@l.g.o
Subject: Re: [gentoo-scm] Git Migration: launch plan & schedule (2015/Aug/08-09)
Date: Thu, 02 Jul 2015 22:05:17
Message-Id: CAGfcS_nCHthazQmz=xgiingaTVgCct9D8cqFhBub1dFjhyr_rA@mail.gmail.com
In Reply to: [gentoo-scm] Git Migration: launch plan & schedule (2015/Aug/08-09) by "Robin H. Johnson"
1 On Thu, Jul 2, 2015 at 5:39 PM, Robin H. Johnson <robbat2@g.o> wrote:
2 > 2015/08/08 15:00 UTC - Freeze
3 > 2015/08/11 - History repo available to graft
4
5 I'm not sure if you already had plans for creating the history, but
6 I've generally been able to turn them around in 12 hours without
7 really trying too hard. I have it all running in a container/chroot
8 where I mount the cvsroot so I could probably get it running on EC2 or
9 elsewhere easily enough if we're in a real hurry. If I had a ton of
10 RAM and store everything in tmpfs then I suspect that it could be done
11 faster - ferringb's design does each package category in a thread so
12 the largest categories become the limiter if you have enough cores (it
13 does them in reverse order by size so the longest ones do start
14 first). At some point the fetching of cvsroots and pushing of git
15 repos becomes limiting - for github the push takes tens of minutes,
16 and the repository takes much longer to show up, though I'm sure that
17 could all be done faster on our infra, either via git push or letting
18 infra clone from a bundle.
19
20 With git replace we don't need the history to go live, and this also
21 means that if we find a mistake in the history we can fix it and issue
22 a new history. So, there isn't really a rush. But, if you don't
23 already have the history conversion taken care of or need it faster, I
24 can take care of it.
25
26 The most recent conversion is at:
27 https://github.com/gentoo/gentoo-gitmig-20150614
28
29 --
30 Rich

Replies

Subject Author
Re: [gentoo-scm] Git Migration: launch plan & schedule (2015/Aug/08-09) "Robin H. Johnson" <robbat2@g.o>