From: Patrick McHardy <kaber@trash.net>
To: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Cc: coreteam@netfilter.org, netfilter-devel@vger.kernel.org
Subject: Re: iptables release
Date: Thu, 29 Nov 2007 08:02:39 +0100 [thread overview]
Message-ID: <474E640F.4010401@trash.net> (raw)
In-Reply-To: <200711290249.lAT2nkEr004081@toshiba.co.jp>
Yasuyuki KOZAKAI wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Tue, 27 Nov 2007 17:52:55 +0100
>
>> 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?
>
> Please wait a few hours at least to release iptables. Just after sending
> this mail, I'll moves some libipt_*.man to libxt_*.man and remove
> libip6t_state.c which I forgot to remove.
Don't worry, I think releasing in time for 2.6.24 would be enough.
BTW, judging by your last batch of xtables patches you seem to have
managed to import the netfilter SVN in git. I keep getting errors
related to paths:
$ git-svnimport -v -C nf.git http://svn.netfilter.org/netfilter
Initialized empty Git repository in /tmp/nf.git/.git/
1: Unrecognized path:
/patch-o-matic-ng/trunk/pptp-conntrack-nat/linux/include/linux/netfilter_ipv4/ip_nat_pptp.h
1: Unrecognized path: /patch-o-matic-ng/trunk/pptp-conntrack-nat/help
1: Unrecognized path:
/patch-o-matic-ng/trunk/pptp-conntrack-nat/linux/include/linux/netfilter_ipv4/ip_conntrack_pptp.h
It seems it switches the first directory and "trunk". Did you use
git-svnimport or just git-svn for importing?
next prev parent reply other threads:[~2007-11-29 7:02 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
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 [this message]
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
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=474E640F.4010401@trash.net \
--to=kaber@trash.net \
--cc=coreteam@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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).