From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Core Team <coreteam@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: iptables release
Date: Tue, 27 Nov 2007 20:04:02 +0100 [thread overview]
Message-ID: <474C6A22.9080202@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711271942330.20371@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Nov 27 2007 17:52, 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.
>>
>> Any opinions?
>
> Apply now, make an rc2 (maybe?),
> apply more gems (coming), target 2.6.25,
> be done :-)
I'm aiming for one release per kernel release to get new stuff
out in time for testing. Unfortunately we're already way behind,
so I'd prefer an earlier release than 2.6.25. My feeling is that
the current -rc works well, so if nobody is aware of any big
issues, I think we should release the current version in a few
weeks when 2.6.24 comes out.
next prev parent reply other threads:[~2007-11-27 19:04 UTC|newest]
Thread overview: 30+ 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 [this message]
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 ` [netfilter-core] " Harald Welte
-- strict thread matches above, loose matches on Subject: below --
2009-09-10 13:29 Patrick McHardy
2009-09-10 17:29 ` Jan Engelhardt
[not found] ` <4AAE7807.8050701@trash.net>
2009-09-14 17:52 ` Jan Engelhardt
2009-09-14 18:07 ` Patrick McHardy
2019-09-10 18:47 Fabio Pedretti
2019-09-11 7:33 ` Fabio Pedretti
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=474C6A22.9080202@trash.net \
--to=kaber@trash.net \
--cc=coreteam@netfilter.org \
--cc=jengelh@computergmbh.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).