From: Bart De Schuymer <bdschuym@pandora.be>
To: Patrick McHardy <kaber@trash.net>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [NETFILTER]: Kill ebt_ulog
Date: Sun, 24 Jul 2005 09:22:51 +0000 [thread overview]
Message-ID: <1122196971.3382.6.camel@localhost.localdomain> (raw)
In-Reply-To: <42E2D0C9.7080808@trash.net>
Op zo, 24-07-2005 te 01:20 +0200, schreef Patrick McHardy:
> > Please add ebt_ulog to Documentation/feature-removal-schedule.txt
> > and give people the usual 6 month grace period to transition to
> > the proposed feature-equivalent alternatives.
>
> It is _broken_ right now and conflicts with ipt_ULOG. There is no
> point in keeping it broken for 6 month.
Removing ebt_ulog would be stupid. So what if it conflicts with
ipt_ULOG, there is no kernel panic, they just can't be used together
currently. That problem should be solved by the generic replacement. To
say that ebt_ulog is broken is plain false.
If the "generic" replacement is such that it can only be used by
iptables modules then it is not generic at all.
Bart
next prev parent reply other threads:[~2005-07-24 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 2:38 [NETFILTER]: Kill ebt_ulog Patrick McHardy
2005-07-23 2:40 ` Patrick McHardy
2005-07-23 11:50 ` Bart De Schuymer
2005-07-23 15:52 ` Patrick McHardy
2005-07-23 19:49 ` Bart De Schuymer
2005-07-23 20:04 ` Patrick McHardy
2005-07-23 21:34 ` Bart De Schuymer
2005-07-23 23:20 ` Patrick McHardy
2005-07-24 17:17 ` Harald Welte
2005-07-23 22:21 ` Carl-Daniel Hailfinger
2005-07-23 23:20 ` Patrick McHardy
2005-07-24 9:22 ` Bart De Schuymer [this message]
2005-07-24 17:25 ` Harald Welte
2005-07-25 0:52 ` David S. Miller
2005-07-25 7:11 ` Bart De Schuymer
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=1122196971.3382.6.camel@localhost.localdomain \
--to=bdschuym@pandora.be \
--cc=kaber@trash.net \
--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.