From: "John W. Linville" <linville@tuxdriver.com>
To: Greg KH <greg@kroah.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
wireless <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Elaboration on "Equivalent fix must already exist in Linus' tree"
Date: Tue, 3 Mar 2009 09:43:45 -0500 [thread overview]
Message-ID: <20090303144345.GA17678@tuxdriver.com> (raw)
In-Reply-To: <20090303062721.GA4091@kroah.com>
On Mon, Mar 02, 2009 at 10:27:21PM -0800, Greg KH wrote:
> And as always, a simple:
> Cc: stable <stable@kernel.org>
> in the patch itself is the easiest way to get it automatically included
> in the next -stable releases after it hits Linus's tree.
>
> What more do people want? Personal invitations?
>
> Is it time to break out the caligraphy pens and wax seals?
Why do you torment me with humor like this?
YES! Of course I want to see how Greg K-H's caligraphy looks.
Just picturing you hunched-over a box of stationary will keep me
humored for days... :-)
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-03-03 14:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 5:43 Elaboration on "Equivalent fix must already exist in Linus' tree" Luis R. Rodriguez
2009-03-03 5:57 ` Jeff Garzik
2009-03-03 6:44 ` Luis R. Rodriguez
2009-03-03 7:20 ` Jeff Garzik
2009-03-03 7:26 ` Greg KH
2009-03-03 7:37 ` Luis R. Rodriguez
2009-03-03 7:42 ` david
2009-03-03 7:57 ` Luis R. Rodriguez
2009-03-03 9:16 ` Theodore Tso
2009-03-03 15:19 ` Stefan Richter
2009-03-03 14:53 ` Greg KH
2009-03-03 15:27 ` Stefan Richter
2009-03-03 17:23 ` Luis R. Rodriguez
2009-03-03 18:13 ` Stefan Richter
2009-03-03 18:43 ` Luis R. Rodriguez
2009-03-03 22:55 ` david
2009-03-03 6:27 ` Greg KH
2009-03-03 14:43 ` John W. Linville [this message]
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=20090303144345.GA17678@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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;
as well as URLs for NNTP newsgroup(s).