From: Legacy Fishtank <garzik@havoc.gtf.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rlimit_nproc
Date: Thu, 27 Dec 2001 16:35:38 -0500 [thread overview]
Message-ID: <20011227163538.D23942@havoc.gtf.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0112271816380.12225-100000@duckman.distro.conectiva> <Pine.LNX.4.33.0112271224590.1167-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0112271224590.1167-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Thu, Dec 27, 2001 at 12:35:38PM -0800
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
next prev parent reply other threads:[~2001-12-27 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 20:18 Rik van Riel
2001-12-27 20:35 ` Linus Torvalds
2001-12-27 21:35 ` Legacy Fishtank [this message]
2001-12-28 23:53 ` Daniel Phillips
2001-12-29 18:13 ` Oliver Xymoron
2001-12-29 18:49 ` Daniel Phillips
2001-12-29 19:12 ` Oliver Xymoron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011227163538.D23942@havoc.gtf.org \
--to=garzik@havoc.gtf.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®