[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: review of modifications of eth-multiplexer

From: olafBuddenhagen
Subject: Re: review of modifications of eth-multiplexer
Date: Sun, 27 Dec 2009 23:17:48 +0100
User-agent: Mutt/1.5.19 (2009-01-05)


On Sun, Dec 27, 2009 at 02:16:40PM +0800, Da Zheng wrote:
> olafBuddenhagen@gmx.net wrote:
> > On Wed, Dec 23, 2009 at 06:32:41PM +0200, Sergiu Ivanov wrote:
> >> On Wed, Dec 23, 2009 at 03:51:16PM +0100, olafBuddenhagen@gmx.net
> >> wrote:

> >>> These are probably all related. It's all part of the network
> >>> virtualization project.

> >> I see.  The question, then, is whether it is appropriate to push
> >> the whole Hurd source tree with Zheng's changes to the incubator,
> >> or would it be better to have a separate repository for that?
> > 
> > I don't see why it should go into the incubator at all. Just put it
> > on a branch in the main repository -- like it was in CVS.

> I think tschwinge wants all new components go to incubator. The main
> repository is only for modified components which has already existed
> in Hurd.

Well, but your project *does* need modifications to existing components
as well! (pfinet and boot) And what's more, these changes in turn make
it depend on at least one of the new components. (devnode) So it's
really not possible to split the "new components" part from the
"modifications to existing components".

Of course, this is all just further indication that such a "no new
components" policy makes no sense whatsoever...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]