Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 27 Dec 2001 16:36:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 27 Dec 2001 16:35:54 -0500 Received: from panic.ohr.gatech.edu ([130.207.47.194]:44438 "HELO havoc.gtf.org") by vger.kernel.org with SMTP id ; Thu, 27 Dec 2001 16:35:40 -0500 Date: Thu, 27 Dec 2001 16:35:38 -0500 From: Legacy Fishtank To: Linus Torvalds Cc: Rik van Riel , linux-kernel@vger.kernel.org Subject: Re: [PATCH] rlimit_nproc Message-ID: <20011227163538.D23942@havoc.gtf.org> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from torvalds@transmeta.com on Thu, Dec 27, 2001 at 12:35:38PM -0800 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 27, 2001 at 12:35:38PM -0800, Linus Torvalds wrote: > Also worthwhile for automation is an md5sum or similar (for verifying that > the mail made it though the mail system unscathed). A pgp signature would > be even better, of course - especially useful as I suspect it would be > good to also cc the things to some patch-list, and having a clear identity > on the sender is always a good idea in these things. I've been thinking that a "patches@kernel.org" dumping ground would be useful. This is NOT intended as a patch tracker. This is NOT intended as a substitution for submitting the patch to you, but instead intended as a patch archive that doesn't go away. We have seen linux-kernel archives come and go, or drop messages. But a patch archive would be useful... I'm not sure a mailing list proper is right for the job, since I want to support the reception and archiving of multi-megabyte patches at times. Jeff - 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/