From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: markmc@redhat.com, netdev@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH] bridge: make bridge-nf-call-*tables default configurable
Date: Wed, 01 Jul 2009 18:05:40 +0200 [thread overview]
Message-ID: <4A4B8954.70803@trash.net> (raw)
In-Reply-To: <20090701.090250.52376308.davem@davemloft.net>
David Miller wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Wed, 01 Jul 2009 12:51:06 +0200
>
>> I agree, this has already caused an endless amount of problems for
>> users due to the unexpected behaviour and, in some cases, bugs.
>>
>> Dave's point is certainly valid as well, until we change the defaults,
>> distributions can use sysctl.conf. But I think we should move towards
>> changing the defaults.
>
> You must do this via something like your suggestion, the
> feature-removal-schedule.txt thing.
Yes, of course. But I prefer the runtime warning (at least on top),
my feeling is not many people actually read feature-removal-schedule.
next prev parent reply other threads:[~2009-07-01 16:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1246379267.3749.42.camel@blaa>
2009-06-30 17:00 ` [PATCH] bridge: make bridge-nf-call-*tables default configurable Herbert Xu
2009-06-30 19:06 ` David Miller
2009-06-30 20:16 ` Jan Engelhardt
2009-06-30 20:57 ` Mark Smith
2009-06-30 21:30 ` Jan Engelhardt
2009-07-01 1:48 ` Herbert Xu
2009-07-01 1:15 ` Herbert Xu
2009-07-01 3:50 ` Jan Engelhardt
2009-07-01 4:10 ` Herbert Xu
2009-07-01 4:14 ` Ben Greear
2009-07-01 9:01 ` Patrick McHardy
2009-07-01 8:57 ` Patrick McHardy
2009-07-01 9:07 ` Herbert Xu
2009-07-01 9:21 ` Patrick McHardy
2009-07-01 16:33 ` Herbert Xu
2009-07-01 17:01 ` Patrick McHardy
2009-07-01 3:16 ` David Miller
2009-07-01 10:45 ` Mark McLoughlin
2009-07-01 10:51 ` Patrick McHardy
2009-07-01 16:02 ` David Miller
2009-07-01 16:05 ` Patrick McHardy [this message]
2009-07-01 16:08 ` David Miller
2009-07-01 21:18 ` Mark Smith
2009-07-01 16:02 ` David Miller
2009-07-01 16:26 ` Herbert Xu
2009-07-01 8:56 ` 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=4A4B8954.70803@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=markmc@redhat.com \
--cc=netdev@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.