From: Dirkjan Ochtman <djc@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Git braindump: 2 of N: developer interaction (merge co-ordinators)
Date: Mon, 4 Jun 2012 08:48:14 +0200 [thread overview]
Message-ID: <CAKmKYaCA-cY0u3abreQNzLdos7r8e396L=_YJJvmL23jumqZNQ@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_nDAH7U1BUDXxu_CczUEHkVKqxfJj6i-tv8Jw1DAyFc7g@mail.gmail.com>
On Sun, Jun 3, 2012 at 9:07 PM, Rich Freeman <rich0@gentoo.org> wrote:
> A test of some sort would cut down the risk of the unexpected when we
> do the real migration.
I understand the desire for this, but I don't think it will work. The
first few hours/days after the git migration are going to be painful
either way. If you run a test now, you'll get limited buy-in
(everyone's busy with other stuff), which would probably also be
rather biased (the most git/DVCS-averse devs are the least likely to
participate). You certainly won't be able to emulate the load of the
real tree.
IMO we should try to be cutting down barriers from the git migration,
not throwing up more. The process has taken long enough already; the
desire to control everything about the migration is part of why it's
taken so long. I lived through Mozilla's Mercurial migration, and it
was messy, too. That was probably worse, as there was less experience
with DVCS at the time, but it will still be messy.
Dirkjan
next prev parent reply other threads:[~2012-06-04 6:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 9:46 [gentoo-dev] Git braindump: 2 of N: developer interaction (merge co-ordinators) Robin H. Johnson
2012-06-03 10:22 ` Andreas K. Huettel
2012-06-03 10:29 ` Robin H. Johnson
2012-06-03 10:36 ` Michael Weber
2012-06-03 10:42 ` Fabio Erculiani
2012-06-03 12:09 ` Thomas Sachau
2012-06-03 16:06 ` Dirkjan Ochtman
2012-06-03 17:02 ` Ulrich Mueller
2012-06-03 17:36 ` Robin H. Johnson
2012-06-03 18:21 ` Dirkjan Ochtman
2012-06-03 19:07 ` Rich Freeman
2012-06-04 6:48 ` Dirkjan Ochtman [this message]
2012-06-04 12:38 ` Rich Freeman
2012-06-04 12:44 ` Dirkjan Ochtman
2012-06-04 3:49 ` Kent Fredric
2012-06-04 13:25 ` Brian Harring
2012-06-04 22:36 ` Michael Weber
2012-06-04 22:57 ` Brian Harring
2012-06-05 1:28 ` Peter Stuge
2012-06-05 7:04 ` Michał Górny
2012-06-05 21:10 ` Brian Harring
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='CAKmKYaCA-cY0u3abreQNzLdos7r8e396L=_YJJvmL23jumqZNQ@mail.gmail.com' \
--to=djc@gentoo.org \
--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