From: John Haxby <john.haxby@oracle.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: SYSRQ in mainline kernel?
Date: Thu, 25 Feb 2010 11:33:05 +0000 [thread overview]
Message-ID: <4B865FF1.8020605@oracle.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1002251220000.4362@obet.zrqbmnf.qr>
On 25/02/10 11:21, Jan Engelhardt wrote:
> On Thursday 2010-02-25 12:08, John Haxby wrote:
>
>> What do I need to do to make this happen (or at least begin to
>> happen)?
>>
> 1. Since it's in Xt-a, you would notify me that you would like me to
> submit it upstream.
>
"I would like to submit SYSRQ upstream, please"
> 2. Bribe the NF maintainer to accept the posted inclusion.
>
I've recently discovered that a local hostelry sells Gales HSB and I'm
willing to stand the NF maintainer a pint of it as a bribe :-)
> 3. ???
> 4. Profit (SCNR!)
>
If there's anything I can do to help, please let me know.
jch
prev parent reply other threads:[~2010-02-25 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 11:08 SYSRQ in mainline kernel? John Haxby
2010-02-25 11:21 ` Jan Engelhardt
2010-02-25 11:33 ` John Haxby [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=4B865FF1.8020605@oracle.com \
--to=john.haxby@oracle.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
/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).