Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Ulrich Mueller <ulm@g.o>
Subject: Re: Git braindump: 2 of N: developer interaction (merge co-ordinators)
Date: Sun, 3 Jun 2012 19:02:31 +0200
>>>>> On Sun, 3 Jun 2012, Dirkjan Ochtman wrote:

> But IMO, discussing this now is a kind of premature optimization.
> We should try to just do the simple thing (everyone commits to the
> main tree), and if there are too many push races we can re-evaluate
> the issue. [...]

And then what? Would returning to CVS be an option?

I for my part would be strongly opposed against a system that doesn't
allow individual devs to push to the tree, and that would involve
"merge lieutenants" or anything similar. So I think these issues must
be discussed before the transition, otherwise a situation could arise
where we were forced to switch to such a system for "technical
reasons".

Ulrich


References:
Git braindump: 2 of N: developer interaction (merge co-ordinators)
-- Robin H. Johnson
Re: Git braindump: 2 of N: developer interaction (merge co-ordinators)
-- Dirkjan Ochtman
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Git braindump: 2 of N: developer interaction (merge co-ordinators)
Next by thread:
Re: Git braindump: 2 of N: developer interaction (merge co-ordinators)
Previous by date:
Re: Git braindump: 2 of N: developer interaction (merge co-ordinators)
Next by date:
Re: Git braindump: 2 of N: developer interaction (merge co-ordinators)


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.