From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: 0/8 Netfilter patches (group 2)
Date: Tue, 08 Apr 2008 18:14:02 +0200 [thread overview]
Message-ID: <47FB99CA.5060002@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0804081803370.2229@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> Those other 8 loose mails (git-send-email has too many flags to get
> it right every time) make up the second group (of two) of kernel
> patches.
>
> ⋮
> ╟ [NETFILTER]: Rename ipt_recent to xt_recent
> ╟ [NETFILTER]: xt_recent: IPv6 support
> ╟ [NETFILTER]: rename NF_ARP to NFPROTO_ARP and assign a non-clashingvalue
> ╟ [NETFILTER]: Implement AF_UNSPEC as a wildcard for extensions
> ╟ [NETFILTER]: Give AF-independent extensions an arpt_ alias
> ╟ [NETFILTER]: Make Ebtables use Xtables infrastructure
> ╟ [NETFILTER]: Collapse tcpmss_reverse_mtu{4,6} into one function
> ╟ [NETFILTER]: Deploy a prefix_length-to-network mask mapping table
> ⋮
> ╙─[master]
Small suggestion for improvement (don't worry, your series
is fine :)): the best ordering for all these patches would
have been:
Set 1: boolean conversions
Set 2: length match (shouldn't have dependencies)
Set 3: recent match (also shouldn't have dependencies)
Set 4: prefix table
Set 5: TCPMSS target
Set 6: ARP-tables patches
This way each logical set of changes can be discussed
seperately. I'd also send things that need additional
userspace-patches (like length) as kernel patch 1-n +
iptables patch 1-n, but closely together.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-04-08 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 16:08 0/8 Netfilter patches (group 2) Jan Engelhardt
2008-04-08 16:14 ` Patrick McHardy [this message]
2008-04-08 16:21 ` Jan Engelhardt
2008-04-08 16:23 ` 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=47FB99CA.5060002@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--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.