From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Forest Bond <forest@alittletooquiet.net>,
Marcos Paulo de Souza <marcos.mage@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6656: Style cleanup of iwctl
Date: Mon, 25 Jun 2012 09:30:41 +0300 [thread overview]
Message-ID: <20120625063041.GL5390@mwanda> (raw)
In-Reply-To: <alpine.LNX.2.00.1206242258230.30361@swampdragon.chaosbits.net>
On Sun, Jun 24, 2012 at 11:01:58PM +0200, Jesper Juhl wrote:
> On Sun, 24 Jun 2012, Dan Carpenter wrote:
> > Nope. It is worth it. Broken out patches are a million times
> > easier to review.
> >
> Ok. I'll redo it as a series. It'll take a little while, so I may not
> finish it tonight, but I'll do it.
>
Thank you for redoing the new broken out version is a lot easier to
review. For many of the patches, I just press my "filter white
space changes" button and the patch shows up as empty. This process
takes me under five seconds. But when it's all tangled up that
change could take minutes to untangle and verify.
> > It frustrates me that you would do things like this when you know
> > the rules. Which part is difficult to understand?
> >
> Nothing is difficult to understand, but breaking this into (for example) a
> series that does:
> 1) fix the indentation to use tabs and not spaces and proper depth
> 2) remove space between cast and variable
> 3) add spaces around operators (like "foo && bar" rather than "foo&&bar")
> 4) add {} to all branches of if statement if one needs it (or remove if none need them)
> would, for many lines, result in all 4 patches changing the same lines.
> That just seemed like a little too much churn for a trivial style cleanup
> patch.
How do I know if it's trivial or not when I can't review it
properly? I think you are saying I should just trust you? That's
not how it works at all.
regards,
dan carpenter
prev parent reply other threads:[~2012-06-25 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 19:45 [PATCH] staging: vt6656: Style cleanup of iwctl Jesper Juhl
2012-06-24 20:47 ` Dan Carpenter
2012-06-24 21:01 ` Jesper Juhl
2012-06-25 6:30 ` Dan Carpenter [this message]
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=20120625063041.GL5390@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.mage@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