Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S285309AbRL2TNA>; Sat, 29 Dec 2001 14:13:00 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S285288AbRL2TMu>; Sat, 29 Dec 2001 14:12:50 -0500
Received: from waste.org ([209.173.204.2]:30673 "EHLO waste.org")
	by vger.kernel.org with ESMTP id <S285269AbRL2TMl>;
	Sat, 29 Dec 2001 14:12:41 -0500
Date: Sat, 29 Dec 2001 13:12:33 -0600 (CST)
From: Oliver Xymoron <oxymoron@waste.org>
To: Daniel Phillips <phillips@bonn-fries.net>
cc: Legacy Fishtank <garzik@havoc.gtf.org>,
        Linus Torvalds <torvalds@transmeta.com>,
        Rik van Riel <riel@conectiva.com.br>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rlimit_nproc
In-Reply-To: <E16KOYH-0000Fr-00@starship.berlin>
Message-ID: <Pine.LNX.4.43.0112291309060.18183-100000@waste.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 Sat, 29 Dec 2001, Daniel Phillips wrote:

> > 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?

Subjects should be human-readable and descriptive. If they're going to
Linux-kernel, they should contain [patch]. I don't think you can
realistically ask for much more unless you put something behind it capable
of rejecting non-conformers.

-- 
 "Love the dolphins," she advised him. "Write by W.A.S.T.E.."

-
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/