From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 30 Jan 2002 05:39:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 30 Jan 2002 05:39:28 -0500 Received: from smtpzilla2.xs4all.nl ([194.109.127.138]:19207 "EHLO smtpzilla2.xs4all.nl") by vger.kernel.org with ESMTP id ; Wed, 30 Jan 2002 05:39:18 -0500 Date: Wed, 30 Jan 2002 11:39:02 +0100 (CET) From: Roman Zippel X-X-Sender: To: Daniel Phillips cc: "Eric W. Biederman" , Linus Torvalds , Larry McVoy , Rob Landley , Subject: Re: A modest proposal -- We need a patch penguin In-Reply-To: Message-ID: 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, Daniel Phillips wrote: > Yes, we should cc our patches to a patchbot: > > patches-2.5@kernel.org -> goes to linus > patches-2.4@kernel.org -> goes to marcello > patches-usb@kernel.org -> goes to gregkh, regardless of 2.4/2.5 > etc. I'd rather make the patchbot more intelligent, that means it analyzes the patch and produces a list of touched files. People can now register to get notified about patches, which changes areas they are interested in. In the simplest configuration nothing would change for Linus, but patches wouldn't get lost and people could be notified if their patch was applied or if it doesn't apply anymore. Other people have a place to search for patches and they can check whether something was already fixed. bye, Roman