mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: william.allen.simpson@gmail.com
Cc: joe@perches.com, brice@myri.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] drivers/net: Move && and || to end of previous line
Date: Sat, 05 Dec 2009 14:21:26 -0800 (PST)	[thread overview]
Message-ID: <20091205.142126.23618243.davem@davemloft.net> (raw)
In-Reply-To: <4B1A557D.4080707@gmail.com>

From: William Allen Simpson <william.allen.simpson@gmail.com>
Date: Sat, 05 Dec 2009 07:43:41 -0500

> These patches should not be accepted to the main Linus tree.

You come out of nowhere as a new contributor.  You have to constantly
ask about policy and other formalities wrt. kernel development.

Yet here you are telling us what should or should not go into the
tree.

You don't even know what the "merge window" is yet you seem so
confident to elicit firm declarations about code policy.

That's nothing but blind arrogance.

Nobody can take you seriously William, really.

And if you think just omitting Joe's patch is going to make your
backporting work any easier, you're mistaken.

Every release we make tons and tons of cleanups and refactorizations
all over the networking and sometimes heavily in TCP.  So you're going
to run into such problems no matter whether Joe's patch goes in or
not.

And like Joe, I think you overstate  how much effort is involved
in such work.  Especially for the size of your patch.

And consider, how in the world do you think it is for me to have to
handle hundreds of patches per day from random people.  If anyone
should get the brunt of the pain, it's me.

Yet I'm ok with it, and you should be too.

  parent reply	other threads:[~2009-12-05 22:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1259001504.16503.79.camel@Joe-Laptop.home>
     [not found] ` <20091123.104130.117837098.davem@davemloft.net>
     [not found]   ` <1259528449.29779.194.camel@Joe-Laptop.home>
     [not found]     ` <20091129.165557.84377714.davem@davemloft.net>
     [not found]       ` <20091130092837.4998f961@nehalam>
2009-12-01  4:13         ` [PATCH] drivers/block/floppy.c: stylistic cleanups Joe Perches
2009-12-01 16:45           ` Stephen Hemminger
2009-12-01 19:09             ` Bartlomiej Zolnierkiewicz
2009-12-01 17:36           ` Marcin Slusarz
2009-12-01 17:46             ` Joe Perches
2009-12-01 18:39           ` Bartlomiej Zolnierkiewicz
     [not found]       ` <1259863101.22783.63.camel@Joe-Laptop.home>
     [not found]         ` <4B190A29.5080905@myri.com>
     [not found]           ` <1259947271.22783.120.camel@Joe-Laptop.home>
2009-12-05 12:43             ` [PATCH net-next-2.6] drivers/net: Move && and || to end of previous line William Allen Simpson
2009-12-05 17:50               ` Joe Perches
2009-12-05 22:05                 ` Jarek Poplawski
2009-12-06  3:36                 ` William Allen Simpson
2009-12-05 22:21               ` David Miller [this message]
2009-12-06  3:00                 ` William Allen Simpson
2009-12-06 17:01                   ` Jonathan Corbet

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=20091205.142126.23618243.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=brice@myri.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=william.allen.simpson@gmail.com \
    /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

Powered by JetHome