All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: next iptables release
Date: Thu, 19 Mar 2009 14:10:23 +0100	[thread overview]
Message-ID: <49C2443F.9080208@netfilter.org> (raw)
In-Reply-To: <49C240DA.2070006@trash.net>

Patrick McHardy wrote:
> Pablo Neira Ayuso wrote:
>> Patrick McHardy wrote:
>>> I've planned to release the next iptables version sometime (late)
>>> this weekend. We've had quite a lot of changes since the last
>>> version, please test the latest version from git and report any
>>> issues.
>>>
>>> Thanks!
>>
>> Great :). BTW, I'm finishing the cluster match manpage, I'll be done
>> tonight, I'd like to see it in this iptables release (even if the
>> feature is expected to appear in 2.6.30).
> 
> I have to ask .. why? :)
>
> Besides potentially confusing people (why doesn't it work despite me
> doing everything the manpage says), what are the advantages of including
> the manpage before the actual implementation?

I planned to distribute the kernel module separately until 2.6.30
arrives, add a page to conntrack-tools.netfilter.org, document this in
the conntrack-tools manual [1] to describe the active-active setup, and
so on. Basically, my motivation is to get some feedback from people as
soon as possible without waiting the whole kernel cycle release.

I know that this seems something exceptional and it may confuse people.
Another choice is to keep it in pom-ng in the meantime, or perhaps
simply be a little bit patient :).

[1] http://conntrack-tools.netfilter.org/manual.html

-- 
"Los honestos son inadaptados sociales" -- Les Luthiers

  reply	other threads:[~2009-03-19 13:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19  8:31 next iptables release Patrick McHardy
2009-03-19 10:01 ` Jan Engelhardt
2009-03-19 10:06   ` Patrick McHardy
2009-03-19 10:13 ` Jan Engelhardt
2009-03-19 11:01 ` Jan Engelhardt
2009-03-19 12:56   ` Patrick McHardy
2009-03-19 12:51 ` Pablo Neira Ayuso
2009-03-19 12:55   ` Patrick McHardy
2009-03-19 13:10     ` Pablo Neira Ayuso [this message]
2009-03-19 13:16       ` Patrick McHardy
2009-03-19 13:52         ` Jan Engelhardt
2009-03-19 13:56           ` Patrick McHardy
2009-03-19 13:45     ` Jan Engelhardt
2009-03-19 13:55       ` Patrick McHardy
2009-03-19 14:02         ` Jan Engelhardt
2009-03-19 14:08           ` Patrick McHardy
2009-03-20 13:24             ` Pablo Neira Ayuso
2009-03-20 14:25               ` Patrick McHardy
2009-03-19 13:55 ` [PATCH] iptables: avoid compile warnings for iptc_insert_chain Christoph Paasch
2009-03-23 12:51   ` Patrick McHardy
2009-03-21 14:46 ` next iptables release Jesper Dangaard Brouer
2009-03-23 13:09   ` Patrick McHardy
  -- strict thread matches above, loose matches on Subject: below --
2009-11-24 11:19 Patrick McHardy
2009-11-24 15:07 Jan Engelhardt
2009-11-24 15:13 ` Patrick McHardy

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=49C2443F.9080208@netfilter.org \
    --to=pablo@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 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.