From: William Allen Simpson <william.allen.simpson@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Brice Goglin <brice@myri.com>, David Miller <davem@davemloft.net>,
netdev@vger.kernel.org,
Linux Kernel Developers <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:36:22 -0500 [thread overview]
Message-ID: <4B1B26B6.2060506@gmail.com> (raw)
In-Reply-To: <1260035440.11126.50.camel@Joe-Laptop.home>
Joe Perches wrote:
> On Sat, 2009-12-05 at 07:43 -0500, William Allen Simpson wrote:
>> My main objection to these sweeping patches is that it makes it much
>> more difficult to maintain and apply patches across different versions of
>> the tree.
>
> I think you underestimate the value of
> standardization and overestimate the
> quantity of work to sort it out for
> the -stable versions.
>
As I mentioned to somebody in private email (having kept rough track), it
took around 9 hours this week for my 8 patch series, spread over 3 days
because of the tedium. Fix rejects, visually check patch against previous
version, compile, test -- at least 1/2 to 1 hour for each numbered patch.
Plus time to resubmit the patch series to the list again.
Of course, that was only for the initial patches already posted to the
list. I've many more -- awaiting approval for the previous set....
Eventually, I have to do the same for each supported -stable version.
Multiply by thousands of contributors.
Hopefully, you did the same, carefully checking your regexp generated
patches visually line by line, and compiling, and testing every driver
in this large patch individually.
I'm not a big believer in making trivial formatting changes and assuming
they work. Or that I didn't fumble fingers somehow. I've made many such
stupid mistakes over the years.
next prev parent reply other threads:[~2009-12-06 3:36 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 [this message]
2009-12-05 22:21 ` David Miller
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=4B1B26B6.2060506@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