Subject: Re: A modest proposal -- We need a patch penguin
To: torvalds@transmeta.com (Linus Torvalds)
Date: Wed, 30 Jan 2002 10:14:49 +0000 (GMT)
Cc: phillips@bonn-fries.net (Daniel Phillips),
        viro@math.psu.edu (Alexander Viro), mingo@elte.hu (Ingo Molnar),
        landley@trommello.org (Rob Landley), linux-kernel@vger.kernel.org,
        riel@conectiva.com.br (Rik van Riel)
In-Reply-To: <Pine.LNX.4.33.0201292326110.1428-100000@penguin.transmeta.com> from "Linus Torvalds" at Jan 29, 2002 11:48:05 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E16VrlR-0006vL-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Sender: linux-kernel-owner@vger.kernel.org

> How many other people are actually using bitkeeper already for the kernel?
> I know the ppc guys have, for a long time, but who else is? bk, unlike
> CVS, should at least be _able_ to handle a "network of people" kind of
> approach.

I gave up on CVS for internal stuff with the -ac patches. I ended up keeping
a running patch and a complete archive of the submissions. The archive so
I can ensure info gets back and forth neatly.

(tangientially further)

Larry - can bitkeeper easily be persuaded to take "messages" back all the way 
to the true originator of a change. Ie if a diff gets to Linus he can reject
a given piece of change and without passing messages back down the chain
ensure they get the reply as to why it was rejected, and even if
nobody filled anything in that it was looked at and rejected by xyz at
time/date ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/