From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: Your new feature should not be enabled by default! -- [torvalds@linux-foundation.org: Re: [GIT] Networking]
Date: Fri, 6 Jan 2012 20:44:49 -0500 [thread overview]
Message-ID: <20120107014449.GF12127@tuxdriver.com> (raw)
Words of wisdom...
----- Forwarded message from Linus Torvalds <torvalds@linux-foundation.org> -----
> Date: Fri, 6 Jan 2012 17:34:39 -0800
> From: Linus Torvalds <torvalds@linux-foundation.org>
> To: David Miller <davem@davemloft.net>
> Cc: akpm@linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
> Subject: Re: [GIT] Networking
>
> On Thu, Jan 5, 2012 at 4:28 PM, David Miller <davem@davemloft.net> wrote:
> >
> > Netlink socket dumping is now supported for UDP and AF_UNIX sockets
> > thanks to Pavel Emelyanov.
>
> .. and this is such a magically important feature that it has to be
> enabled by default?
>
> It's something that has never been supported before, how did it
> suddenly become 'default y' after twenty years of not even being an
> issue?
>
> It's a disease, I tell you, to think that new features are important.
> Stop it. Tell people you take patches from to stop it. If we haven't
> needed them before, they sure as hell aren't suddenly "Say Yes if you
> don't know" material.
>
> Please fix this, but more importantly, please try to fix *people*. So
> I don't have to always react to the stupid new "default y" options.
>
> Linus
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
----- End forwarded message -----
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next reply other threads:[~2012-01-07 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 1:44 John W. Linville [this message]
2012-01-07 1:50 ` Your new feature should not be enabled by default! -- [torvalds@linux-foundation.org: Re: [GIT] Networking] David Miller
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=20120107014449.GF12127@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox