From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: astralstorm@gorzow.mm.pl, mkrufky@m1k.net, linux-kernel@vger.kernel.org
Subject: Re: MM kernels - how to keep on the bleeding edge?
Date: Fri, 29 Jul 2005 19:39:52 -0700 [thread overview]
Message-ID: <20050729193952.125d1377.pj@sgi.com> (raw)
In-Reply-To: <20050726161149.0c9c36fa.akpm@osdl.org>
Andrew wrote:
> Ho hum. Adding a "why
> this was dropped" to the email seemed too tricky.
I can't speak for all the other clue deprived gits out here, but for
me at least just adding a generic "If this patch was sent on to Linus,
that might be one possible reason it is now dropped from *-mm." boiler
plate sentence to the existing notice would have been sufficient to
calm my nerves and stop me from pestering you with stupid "what what
why did you kill my patch ?!?" queries.
No need for articial intelligence to condition the message on whether
the patch actually was sent to Linus, or not.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-07-30 2:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 16:58 MM kernels - how to keep on the bleeding edge? Radoslaw AstralStorm Szkodzinski
2005-07-26 19:45 ` Michael Krufky
2005-07-26 20:15 ` Radoslaw AstralStorm Szkodzinski
2005-07-26 20:26 ` Michael Krufky
2005-07-26 21:41 ` Andrew Morton
2005-07-26 22:32 ` Andrew Morton
2005-07-26 22:52 ` Radoslaw AstralStorm Szkodzinski
2005-07-26 22:49 ` Radoslaw AstralStorm Szkodzinski
2005-07-26 23:11 ` Andrew Morton
2005-07-26 23:25 ` Radoslaw AstralStorm Szkodzinski
2005-07-26 23:35 ` Andrew Morton
2005-07-26 23:54 ` Randy Dunlap
2005-07-27 0:00 ` Radoslaw AstralStorm Szkodzinski
2005-07-27 0:08 ` Andrew Morton
2005-07-30 2:39 ` Paul Jackson [this message]
2005-07-27 0:40 ` Michael Krufky
2005-07-27 1:02 ` Michael Krufky
2005-07-27 1:04 ` Andrew Morton
2005-07-27 1:13 ` Michael Krufky
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=20050729193952.125d1377.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=astralstorm@gorzow.mm.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@m1k.net \
/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