public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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 14:44:15 +0200	[thread overview]
Message-ID: <CAKmKYaD3uYW3n9R7-bhBYr-JxVVUXzXaaVv+B7GVyriS42LnWQ@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_nRbuWNN=MAdH1C1ssjQFv40kXz2z5mUwMjSwiqx0=hBw@mail.gmail.com>

On Mon, Jun 4, 2012 at 2:38 PM, Rich Freeman <rich0@gentoo.org> wrote:
> On Mon, Jun 4, 2012 at 2:48 AM, Dirkjan Ochtman <djc@gentoo.org> wrote:
>> 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.
>
> Fair enough.
>
> We should also be asking ourselves what happens if something goes
> really wrong and there are no commits for a whole two days.  I think
> the answer is, not much.  As long as there are a few devs who can tend
> to security issues or whatever I don't see it as an issue if we have
> the odd glitch.

That's what I was thinking, too. :)

> We do need to get the docs up so that we're at least somewhat
> harmonized on conventions (authors vs committers, and so on).  Let's
> not burn the first person to make a mistake at the stake either...

Yeah, some initial tutorial of how to get going would probably help a
lot. For everything else, there's IRC (and hopefully most of what's
discussed there would soon find it's way into the HOWTO doc).

Cheers,

Dirkjan



  reply	other threads:[~2012-06-04 12:45 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
2012-06-04 12:38           ` Rich Freeman
2012-06-04 12:44             ` Dirkjan Ochtman [this message]
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=CAKmKYaD3uYW3n9R7-bhBYr-JxVVUXzXaaVv+B7GVyriS42LnWQ@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