From: Harald Welte <laforge@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Netfilter Core Team <coreteam@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: [netfilter-core] iptables release
Date: Thu, 29 Nov 2007 18:46:55 +0100 [thread overview]
Message-ID: <20071129174655.GK9579@prithivi.gnumonks.org> (raw)
In-Reply-To: <474C4B67.3000200@trash.net>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On Tue, Nov 27, 2007 at 05:52:55PM +0100, Patrick McHardy wrote:
> I have a large number of pending patches for iptables for new
> matches and targets. I'm not going apply patches for new things
> unless they are at least in a -rc kernel, so we have a chance to
> fix mistakes. So my question is whether we're ready to release
> the current iptables -rc anytime soon (before/when 2.6.24 is
> released) or whether we're more likely going to need until 2.6.25,
> in which case I would apply them now.
I have a number of manpage updates pending, unfortunately I still can't
commit to the repository (and since it includes many file renames it's
hard to just submit a patch).
I'd prefer if the release is held back until the documentation is in
sync.
--
- Harald Welte <laforge@netfilter.org> http://netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-11-29 18:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 16:52 iptables release Patrick McHardy
2007-11-27 18:57 ` Jan Engelhardt
2007-11-27 19:04 ` Patrick McHardy
2007-11-28 17:49 ` Jan Engelhardt
2007-11-27 21:58 ` Jesper Dangaard Brouer
2007-11-28 8:30 ` Patrick McHardy
2007-11-29 2:49 ` Yasuyuki KOZAKAI
2007-11-29 6:00 ` Yasuyuki KOZAKAI
[not found] ` <200711290249.lAT2nkEr004081@toshiba.co.jp>
2007-11-29 7:02 ` Patrick McHardy
2007-11-29 8:01 ` Yasuyuki KOZAKAI
2007-11-29 8:10 ` Jan Engelhardt
2007-11-29 8:27 ` Patrick McHardy
2007-11-29 8:47 ` Jan Engelhardt
2007-11-29 9:07 ` Jan Engelhardt
2007-11-29 9:13 ` Patrick McHardy
2007-11-29 9:19 ` Jan Engelhardt
2007-11-29 9:25 ` Patrick McHardy
2007-11-29 20:46 ` Jesper Dangaard Brouer
2007-11-29 20:52 ` Patrick McHardy
2007-11-29 21:05 ` Jan Engelhardt
2007-11-29 21:37 ` Patrick McHardy
2007-11-30 17:37 ` Yasuyuki KOZAKAI
[not found] ` <200711301737.lAUHbXWh002545@toshiba.co.jp>
2007-11-30 17:49 ` Jan Engelhardt
2007-11-29 17:46 ` Harald Welte [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=20071129174655.GK9579@prithivi.gnumonks.org \
--to=laforge@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=kaber@trash.net \
--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).