Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 23 Apr 2002 02:06:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 23 Apr 2002 02:06:41 -0400 Received: from pc-62-30-255-50-az.blueyonder.co.uk ([62.30.255.50]:9344 "EHLO kushida.apsleyroad.org") by vger.kernel.org with ESMTP id ; Tue, 23 Apr 2002 02:06:40 -0400 Date: Tue, 23 Apr 2002 07:04:17 +0100 From: Jamie Lokier To: Daniel Phillips Cc: Jeff Garzik , Rasmus Andersen , CaT , Larry McVoy , Anton Altaparmakov , linux-kernel@vger.kernel.org Subject: Re: Suggestion re: [PATCH] Remove Bitkeeper documentation from Linux tree Message-ID: <20020423070417.A19987@kushida.apsleyroad.org> In-Reply-To:

<20020421143038.H8142@havoc.gtf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Daniel Phillips wrote: > In fact, the basic premise is that people mail to the patchbot, not the > maintainer. The patchbot knows who the maintainer is and forwards the patch > to the maintainer, using the maintainer's format of choice, or as now > proposed, just drops it into the BK repository and forwards a notification, > both to the maintainer and the linux-patches list. Oh, now that _is_ a good idea. So individuals like me can register and say "notify me if anyone posts something for net/packet/* or include/linux/if_packet.h". Whether I'm a maintainer or not? That would be pretty useful. An uber-feature would be "notify me if the VFS interface or locking rules change", for version 2 perhaps ;-) -- Jamie - 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/