Date: Tue, 6 Sep 2005 19:38:07 -0700
From: Paul Jackson <pj@sgi.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: akpm@osdl.org, bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-mm1
Message-Id: <20050906193807.472228b5.pj@sgi.com>
In-Reply-To: <9a87484905090617444e89722d@mail.gmail.com>
References: <20050901035542.1c621af6.akpm@osdl.org>
	<20050903122126.GM3657@stusta.de>
	<20050903123410.1320f8ab.akpm@osdl.org>
	<20050903195423.GP3657@stusta.de>
	<20050903130632.3124e19b.akpm@osdl.org>
	<9a87484905090414245589a3c@mail.gmail.com>
	<20050904143033.13a4bed3.akpm@osdl.org>
	<20050906170513.60ed024a.pj@sgi.com>
	<9a87484905090617444e89722d@mail.gmail.com>
Organization: SGI
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 953
Lines: 25

Jesper wrote:
> Something like that would be just fine for the
> patches that have been sent on to Linus.

No - not just the patches sent to Linus - that's a burden on Andrew to
separate things out.

Andrew can put the boiler plate statement on _all_ drop messages

>         If I just sent the patch to Linus, that is
>         probably why I dropped it here.

At the very least, he gets to cuss us out for not being able to read,
instead of not being able to associate the 'patch to Linus' message with
the 'drop' message a few hours later.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401
-
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/