From: John Haxby <john.haxby@oracle.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Where to post patches to xtables-addons?
Date: Fri, 25 Jun 2010 10:23:43 +0100 [thread overview]
Message-ID: <4C24759F.8060008@oracle.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1006241916270.324@obet.zrqbmnf.qr>
On 24/06/10 18:19, Jan Engelhardt wrote:
>> Is that why my xt_SYSRQ patch seems to have been ignored?
>>
> The last mail from you in my collections is "Whither xt_SYSRQ" from May
> 14. Whereever you sent it to, it was neither nf(-user) nor nf-dev, nor
> was I cc'ed - that's the technical answer.
>
Some mail server somewhere doesn't like me :-( I don't think I'm quite
losing my marbles though, at least not yet:
http://markmail.org/thread/4pe7wz34gxnt52hb
Would you like me to re-send?
jch
next prev parent reply other threads:[~2010-06-25 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 15:47 Where to post patches to xtables-addons? John Haxby
2010-06-24 17:19 ` Jan Engelhardt
2010-06-25 9:23 ` John Haxby [this message]
2010-06-25 9:28 ` Jan Engelhardt
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=4C24759F.8060008@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.