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 Development <gentoo-dev@g.o>
From: Christian Faulhammer <fauli@g.o>
Subject: Re: [git migration] The problem of ChangeLog generation
Date: Mon, 21 Jun 2010 21:34:48 +0200
Hi,

Richard Freeman <rich0@g.o>:
> Having branches to do development and facilitate access and testing 
> seems fine, however we should always have the goal of getting these 
> tested revisions merged back into the main tree.  We really don't
> want divergent development to be the norm.

 Right, the extensive use of overlays shows a clear problem here.
Users could work on a branch of the normal tree to bring in their
changes, which gets merged by a normal developer at some point.  The
offical dev-lisp category is in bad shape (== not usable at all), while
the overlay is in great condition because of some dedicated users.

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://www.faulhammer.org/>
Attachment:
signature.asc (PGP signature)
References:
[git migration] The problem of ChangeLog generation
-- Nirbheek Chauhan
Re: [git migration] The problem of ChangeLog generation
-- Angelo Arrifano
Re: [git migration] The problem of ChangeLog generation
-- Richard Freeman
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: [git migration] The problem of ChangeLog generation
Next by thread:
Re: [git migration] The problem of ChangeLog generation
Previous by date:
Re: My council manifesto
Next by date:
Re: Gentoo Council 2010/2011 - Nominations are now open


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.