From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: iptables release plans
Date: Mon, 21 Mar 2011 23:44:07 +0100 [thread overview]
Message-ID: <4D87D4B7.5000404@trash.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1103212207450.23334@blackhole.kfki.hu>
On 21.03.2011 22:09, Jozsef Kadlecsik wrote:
> On Mon, 21 Mar 2011, Patrick McHardy wrote:
>
>> About a potential iptables release for 2.6.38 - we don't have any
>> new features in the kernel that would require a new release.
>> However we've had a lot of other changes that would be good to
>> get out for wider testing.
>>
>> Unfortunately due some confusion at the time of the last kernel
>> release, all patches for the upcoming feature in 2.6.39 have been
>> added to the master branch. I don't want to release extensions
>> for new kernel features while we're in the -rc phase since we
>> might still decide to change the userspace API.
>>
>> So the options basically are:
>>
>> - branch off the current HEAD, remove all new extension for upcoming
>> features and release that branch
>>
>> - skip the release for 2.6.38
>>
>> Any opinions?
>
> I don't really like either one, but if we have to choose then the first
> one seems better. At least the release will contain the bugfixes.
Yeah, it certainly was a mistake, but to me the first option
seems better as well.
Thanks!
prev parent reply other threads:[~2011-03-21 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 18:48 iptables release plans Patrick McHardy
2011-03-21 19:48 ` Jan Engelhardt
2011-03-21 22:43 ` Patrick McHardy
2011-03-21 23:22 ` Jan Engelhardt
2011-03-21 21:09 ` Jozsef Kadlecsik
2011-03-21 22:44 ` Patrick McHardy [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=4D87D4B7.5000404@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--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.