public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Allen Simpson <william.allen.simpson@gmail.com>
To: David Miller <davem@davemloft.net>
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 22:00:41 -0500	[thread overview]
Message-ID: <4B1B1E59.1030307@gmail.com> (raw)
In-Reply-To: <20091205.142126.23618243.davem@davemloft.net>

David Miller wrote:
> 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.
> 
Because they are not documented.  Oh, and a reminder -- you've not
answered my most recent questions....


> 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

That would be one of the questions (which git clone to patch against now)
that you haven't answered.  Silly of me to ask practical questions.


> confident to elicit firm declarations about code policy.
> 
That would be because I've ample experience coding for multiple open
source platforms.  Apparently such experience isn't valued (by you).

But the fact that about 19% of the Linux code base has managed to function
for circa 18 years without this particular coding policy might be a clue!


> That's nothing but blind arrogance.
> 
> Nobody can take you seriously William, really.
> 
Always _such_ a delight interacting with you, and your personal attacks.

Something that *is* in Documentation/ManagementStyle at 147:

     There's just a few simple rules here:
      (1) don't call people d*ckheads (at least not in public)
      (2) learn how to apologize when you forgot rule (1)

  reply	other threads:[~2009-12-06  3:00 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
2009-12-06  3:00                 ` William Allen Simpson [this message]
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=4B1B1E59.1030307@gmail.com \
    --to=william.allen.simpson@gmail.com \
    --cc=brice@myri.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox