From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: kaber@netfilter.org,
Netfilter Developer Mailing List
<netfilter-devel@lists.netfilter.org>
Subject: Re: Maintenance for POM-ng modules
Date: Thu, 07 Dec 2006 04:08:28 +0100 [thread overview]
Message-ID: <457785AC.6070105@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0612062122410.16042@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> Hi,
>
> connlimit:
> As of r6652, it has been moved to external. I would like to see it in
> pomng again (or even mainline kernel).
IIRC it scans the conntrack table. This general opinion so far has
been that this should not be merged, but I'm personally not that
opposed since I don't really see a better way and the functionality
seems useful (and I don't really want to lecture people on whats bad
for them, it should just be documented).
> XOR:
> Removed as of r6598, reason: no maintainer. I am currently maintaining
> it in private, just for the fun of it.
We definitely don't want to merge this :)
> unclean:
> Also deleted as of r6598. I would like to revive this module since it
> will be useful to us.
This one is considered harmful by all netfilter developers and the
many bugs so far breaking totally legitimate behaviour proof this
right. This is also why it has been removed in 2.6.
> So, given this short summary, I would like to take these three projects
> and bring them back into shape (they really don't need a lot fixing
> AFAICT).
> What's the preferred procedure?
For patches that we don't want to merge but see some use in, an
external pom repository is prefered. Its basically a tar of the
patchlet directory with repository: changed to "external" in the
info file. So for the connlimit match feel free so send me a URL
for an external repository or convince me that it should be
merged, the others should probably just be deleted :)
prev parent reply other threads:[~2006-12-07 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 20:48 Maintenance for POM-ng modules Jan Engelhardt
2006-12-07 3:08 ` Patrick McHardy [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=457785AC.6070105@trash.net \
--to=kaber@trash.net \
--cc=jengelh@linux01.gwdg.de \
--cc=kaber@netfilter.org \
--cc=netfilter-devel@lists.netfilter.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.