From: Patrick McHardy <kaber@trash.net>
To: Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>,
"'netfilter@vger.kernel.org'" <netfilter@vger.kernel.org>,
netfilter-announce@lists.netfilter.org, netfilter-cor
Subject: [ANNOUNCE] Release of iptables 1.4.1-rc3
Date: Fri, 06 Jun 2008 13:37:13 +0200 [thread overview]
Message-ID: <48492169.6060300@trash.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
The netfilter coreteam proudly presents:
iptables version 1.4.1-rc3
The hopefully final release candidate for 1.4.1. Actually I already
wanted to have released 1.4.1 by now, but my notebook broke last
week during travel, which caused some delays.
This release candidate includes some minor fixes, manpage updates
and a full resync of the kernel header files to fix the build on
old systems that don't have all headers or miss the endian annotated
types. The header resync is the main reason for having this release
candidate since it has some risk of introducing new compilation
breakage. So even if you can't do real functional testing, please
verify whether it compiles cleanly for you.
Version 1.4.1-rc3 can be obtained from (please note that the
webpage hasn't been rebuilt yet, but will be shortly):
http://www.netfilter.org/projects/iptables/downloads.html
ftp://ftp.netfilter.org/pub/iptables/
git://git.netfilter.org/iptables.git
On behalf of the Netfilter Core Team.
Happy testing!
[-- Attachment #2: changes-iptables-1.4.1-rc3.txt --]
[-- Type: text/plain, Size: 340 bytes --]
Jan Engelhardt (2):
Update .gitignore
build: check for missing feature files
Patrick McHardy (2):
manpages: consistent syntax
Resync header files with kernel
Thomas Jarosch (1):
Add xtables version defines.
Yasuyuki Kozakai (1):
Use s6_addr32 to access bits in int6_addr instead of incompatible name
reply other threads:[~2008-06-06 11:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48492169.6060300@trash.net \
--to=kaber@trash.net \
--cc=netfilter-announce@lists.netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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