From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nftables: tar packages
Date: Sun, 3 Nov 2013 18:45:06 +0100 [thread overview]
Message-ID: <20131103174506.GA3836@localhost> (raw)
In-Reply-To: <52757AD7.30204@gmail.com>
On Sat, Nov 02, 2013 at 11:21:11PM +0100, Xose Vazquez Perez wrote:
> hi Pablo/Patrick,
>
> Are you going to do tar packages of nftables [1]
> infrastructure (libnftables, nftables, iptables-nftables) ?
>
> Or just only git ?
You can fetch daily snapshots via:
ftp://ftp.netfilter.org/pub/libnftables/snapshot/
ftp://ftp.netfilter.org/pub/nftables/snapshot/
Remember that the first expected Linux kernel version including
nftables is *3.13*.
The iptables-nftables tree is planned to be merged into iptables by
when 3.13-rc1 will be released.
The library ABI will freeze by when 3.13 will be released, meanwhile
expect ABI breakages. My recommendation, at this stage, is that you
keep fresh paired installations of libnftables and nftables to avoid
troubles.
prev parent reply other threads:[~2013-11-03 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 22:21 nftables: tar packages Xose Vazquez Perez
2013-11-03 17:45 ` Pablo Neira Ayuso [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=20131103174506.GA3836@localhost \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=xose.vazquez@gmail.com \
/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.