From: Patrick McHardy <kaber@trash.net>
To: Tom Eastep <teastep@shorewall.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [Patch] ipsec-nat patches for 2.6.9
Date: Tue, 14 Dec 2004 22:31:37 +0100 [thread overview]
Message-ID: <41BF5BB9.5090901@trash.net> (raw)
In-Reply-To: <1103050024.22667.34.camel@ursa.shorewall.net>
Tom Eastep wrote:
>What is the timeline for getting these patches (and policy match) into
>the kernel.org tree? The next major release of Shorewall relies on them
>for native 2.6 IPSEC support.
>
>
I will submit them once 2.6.10 is out.
Regards
Patrick
next prev parent reply other threads:[~2004-12-14 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 8:19 [Patch] ipsec-nat patches for 2.6.9 Ronald Moesbergen
2004-12-14 18:47 ` Tom Eastep
2004-12-14 21:31 ` Patrick McHardy [this message]
2005-01-05 1:11 ` [Patch] ipsec-nat patches for 2.6.10 (was: ipsec-nat patches for 2.6.9) Robert Dahlem
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=41BF5BB9.5090901@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=teastep@shorewall.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 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.