Re: [PATCH] rlimit_nproc

[Daniel Phillips <phillips@bonn-fries.net>]

On December 29, 2001 07:13 pm, Oliver Xymoron wrote:
> On Sat, 29 Dec 2001, Daniel Phillips wrote:
> 
> > On December 27, 2001 10:35 pm, Legacy Fishtank wrote:
> > > 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.
> >
> > Exactly what I was thinking of: 'linux-patches@kernel.org'.  The idea is,
> > instead of putting [PATCH] on your subject line and cc'ing it to Linus, you
> > mail it to linux-patches with a cc to lkml if you like (depending on size of
> > patch, how interesting, etc).  In any event, linux-patches will forward a
> > copy to Linus.
> 
> You of course need something like -2.4 and -2.5.

Yes:

    linux-patches-2.0@kernel.org
    linux-patches-2.2@kernel.org
    linux-patches-2.4@kernel.org
    linux-patches-2.5@kernel.org

Now... conventions for the subject line?

By the way, this to me is really a 'bot'.  The bulk of the proposals in this
thread seem more like tools.

--
Daniel