Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S289182AbSA3NAa>; Wed, 30 Jan 2002 08:00:30 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S289179AbSA3NAU>; Wed, 30 Jan 2002 08:00:20 -0500
Received: from smtpzilla1.xs4all.nl ([194.109.127.137]:9990 "EHLO
	smtpzilla1.xs4all.nl") by vger.kernel.org with ESMTP
	id <S289175AbSA3NAP>; Wed, 30 Jan 2002 08:00:15 -0500
Date: Wed, 30 Jan 2002 13:59:56 +0100 (CET)
From: Roman Zippel <zippel@linux-m68k.org>
X-X-Sender: <roman@serv>
To: Jeff Garzik <garzik@havoc.gtf.org>
cc: Rob Landley <landley@trommello.org>, Miles Lane <miles@megapathdsl.net>,
        Chris Ricker <kaboom@gatech.edu>,
        World Domination Now! <linux-kernel@vger.kernel.org>
Subject: Re: A modest proposal -- We need a patch penguin
In-Reply-To: <20020130034746.K32317@havoc.gtf.org>
Message-ID: <Pine.LNX.4.33.0201301350020.7674-100000@serv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Hi,

On Wed, 30 Jan 2002, Jeff Garzik wrote:

> Instead of doing this stuff half-assed, just convince Linus to use BK :)

I don't care what Linus uses, but Linus decision should not lock other
developers into using the same tools, e.g. it should not become
inconvenient to send simple patches. The basic communication tools should
still be mail and patches. What we IMO need is a patch management system
not a source management system.

bye, Roman

-
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/