Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 31 Jan 2002 08:52:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 31 Jan 2002 08:52:43 -0500 Received: from garrincha.netbank.com.br ([200.203.199.88]:48134 "HELO netbank.com.br") by vger.kernel.org with SMTP id ; Thu, 31 Jan 2002 08:52:29 -0500 Date: Thu, 31 Jan 2002 11:51:53 -0200 (BRST) From: Rik van Riel X-X-Sender: To: Stuart Young Cc: , Roman Zippel , "Eric W. Biederman" , Linus Torvalds , Larry McVoy , Rob Landley , Daniel Phillips , Rasmus Andersen , Subject: Re: Wanted: Volunteer to code a Patchbot In-Reply-To: <5.1.0.14.0.20020131114402.02653b10@mail.amc.localnet> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org 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 On Thu, 31 Jan 2002, Stuart Young wrote: > Possibly, but then it'll reply to the spammer and you'll get bounces left > and right. Perhaps it's a simple case that the patcher submitting will have > to have registered the email address before submitting their patch. Only > needs to be done once (not every time a patch is submitted, that's mad!), > and weeds out the noise. -------------------------------------------------------------- This is the patchbot auto-reply. You tried to send me a patch (attached below) but I don't know you. To confirm that you exist (and aren't a spammer) please reply to this message. After receiving your reply your queued patches will be published. -------------------------------------------------------------- Rik -- "Linux holds advantages over the single-vendor commercial OS" -- Microsoft's "Competing with Linux" document http://www.surriel.com/ http://distro.conectiva.com/ - 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/