From: Rich Freeman <rich0@gentoo.org>
To: gentoo-scm@lists.gentoo.org
Subject: Re: [gentoo-scm] Git Migration: launch plan & schedule (2015/Aug/08-09)
Date: Thu, 2 Jul 2015 18:05:10 -0400 [thread overview]
Message-ID: <CAGfcS_nCHthazQmz=xgiingaTVgCct9D8cqFhBub1dFjhyr_rA@mail.gmail.com> (raw)
In-Reply-To: <robbat2-20150702T212736-634219990Z@orbis-terrarum.net>
On Thu, Jul 2, 2015 at 5:39 PM, Robin H. Johnson <robbat2@gentoo.org> wrote:
> 2015/08/08 15:00 UTC - Freeze
> 2015/08/11 - History repo available to graft
I'm not sure if you already had plans for creating the history, but
I've generally been able to turn them around in 12 hours without
really trying too hard. I have it all running in a container/chroot
where I mount the cvsroot so I could probably get it running on EC2 or
elsewhere easily enough if we're in a real hurry. If I had a ton of
RAM and store everything in tmpfs then I suspect that it could be done
faster - ferringb's design does each package category in a thread so
the largest categories become the limiter if you have enough cores (it
does them in reverse order by size so the longest ones do start
first). At some point the fetching of cvsroots and pushing of git
repos becomes limiting - for github the push takes tens of minutes,
and the repository takes much longer to show up, though I'm sure that
could all be done faster on our infra, either via git push or letting
infra clone from a bundle.
With git replace we don't need the history to go live, and this also
means that if we find a mistake in the history we can fix it and issue
a new history. So, there isn't really a rush. But, if you don't
already have the history conversion taken care of or need it faster, I
can take care of it.
The most recent conversion is at:
https://github.com/gentoo/gentoo-gitmig-20150614
--
Rich
next prev parent reply other threads:[~2015-07-02 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 21:39 [gentoo-scm] Git Migration: launch plan & schedule (2015/Aug/08-09) Robin H. Johnson
2015-07-02 22:05 ` Rich Freeman [this message]
2015-07-03 0:51 ` Robin H. Johnson
2015-07-03 1:26 ` Rich Freeman
2015-08-08 17:47 ` [gentoo-scm] Re: [gentoo-dev] " Robin H. Johnson
2015-08-09 5:36 ` [gentoo-scm] Git Migration: go-live! Robin H. Johnson
[not found] ` <55C716C1.5050403@gentoo.org>
[not found] ` <20150809093112.GB28996@schiffbauer.net>
2015-08-09 10:02 ` [gentoo-scm] Re: [gentoo-core] [gentoo-dev] " Mike Frysinger
[not found] ` <55C725BB.1060500@gentoo.org>
[not found] ` <20150809131619.d6f957b30ed09cc5aa35f65c@gentoo.org>
2015-08-09 21:04 ` [gentoo-scm] " Robin H. Johnson
[not found] ` <26679488.1voUmlKOLj@arcadia>
2015-08-09 10:46 ` [gentoo-scm] Re: [gentoo-core] " Mike Frysinger
2015-08-09 11:54 ` [gentoo-scm] Re: [gentoo-dev] " Alexey Shvetsov
2015-08-09 12:43 ` Mike Frysinger
2015-08-09 13:10 ` Rich Freeman
2015-08-09 14:56 ` Robin H. Johnson
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='CAGfcS_nCHthazQmz=xgiingaTVgCct9D8cqFhBub1dFjhyr_rA@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-scm@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