All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [RFC PATCH IPTABLES 0/12]: matches/targets unification
Date: Wed, 06 Dec 2006 18:40:19 +0100	[thread overview]
Message-ID: <45770083.306@trash.net> (raw)
In-Reply-To: <200612061233.kB6CXNxL024591@toshiba.co.jp>

Yasuyuki KOZAKAI wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Wed, 06 Dec 2006 11:25:58 +0100
> 
>>So, what I'm proposing is to remove all extensions that are
>>neither part of 2.4 or 2.6 from iptables, pushing those for
>>externally maintained patches to the patch maintainers, those
>>for patches maintained in pom to pom, and delete the rest.
> 
> 
> I agree.
> 
> 
>>Comments?
> 
> 
> 'make' should test whether kernel supports extensions or not.

Yes, that would be an alternative (currently some do, some don't).
But the testing and maintenance problems would still persist.

> Do distributors manually change -test[6] scripts and build them
> these days ? Or you mean that distributors apply kernel patch to their
> kernel as well ? In later case, that means that they definitely want to
> support features. Then even if we moves them from source tree of iptables,
> I think they will apply them and same things will happen.

The later. In that case its out of our control of course, but currently
we are encouraging it by building unsupported extensions by default.

> But anyway, I think it's good idea to move extensions which is not
> supported by mainline kernel.

I'm going to go over them in the next days and make a list of those
to be deleted/pushed to patch maintainers.

  parent reply	other threads:[~2006-12-06 17:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30  9:43 [RFC PATCH IPTABLES 0/12]: matches/targets unification Yasuyuki KOZAKAI
2006-11-30 13:35 ` Patrick McHardy
2006-12-03  4:36 ` Yasuyuki KOZAKAI
2006-12-06 10:25 ` Patrick McHardy
2006-12-06 12:33   ` Yasuyuki KOZAKAI
     [not found]   ` <200612061233.kB6CXNxL024591@toshiba.co.jp>
2006-12-06 17:40     ` Patrick McHardy [this message]
2006-12-06 20:49   ` Martin Josefsson
2006-12-07  3:09     ` Patrick McHardy
     [not found] <b317600c0704110750x30861e6ft6cd0a53d415cba74@mail.gmail.com>
2007-04-11 14:52 ` Time module included in the default Fedora Fred Trotter
2007-04-11 15:58   ` Jan Engelhardt
2007-04-11 16:33     ` Patrick McHardy
2007-04-11 17:15       ` Fred Trotter
2007-04-11 17:34       ` Jan Engelhardt
2007-04-11 17:44         ` Patrick McHardy
2007-04-11 17:44           ` Patrick McHardy
2007-04-11 17:55     ` Pascal Hambourg

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=45770083.306@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.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 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.