From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] posix-aio-compat: Expand tabs that have crept in
Date: Thu, 27 May 2010 15:46:38 +0200 [thread overview]
Message-ID: <4BFE77BE.4040808@redhat.com> (raw)
In-Reply-To: <20100527131233.GA3584@stefan-thinkpad.transitives.com>
Am 27.05.2010 15:12, schrieb Stefan Hajnoczi:
> On Thu, May 27, 2010 at 02:50:54PM +0200, Kevin Wolf wrote:
>> I'm usually not a big supporter of patches that only change style, but
>> tabs are nasty and you can ignore these whitespace changes in git blame
>> at least, so for all I care let's take it for once.
>
> Interesting, I tend to prefer separate code change and whitespace change
> patches. It's hard to review a patch that combines code and whitespace
> changes because you have to manually compare the touched lines to see
> what, if anything, has changed.
That's not what I mean either. I usually avoid any style fixes in code
that I don't touch otherwise. So when I need to fix an if condition
anyway, I can add missing braces there as well, but I wouldn't write a
patch that adds braces everywhere.
The main reason is that it would break git blame output by listing some
completely unrelated style fixes instead of the patch that really added
or semantically changed the line. Whitespace changes are not quite as
bad, though, as there is git blame -w.
> Is this the policy across all of QEMU or your preference for
> block-related code? I'll try to follow it for that area in the future.
I don't think it's written down explicitly, but I remember some
discussion about style fixes which basically resulted in "do new code
right, leave old code alone".
Kevin
next prev parent reply other threads:[~2010-05-27 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 11:52 [Qemu-devel] [PATCH] posix-aio-compat: Expand tabs that have crept in Stefan Hajnoczi
2010-05-27 12:50 ` Kevin Wolf
2010-05-27 13:12 ` Stefan Hajnoczi
2010-05-27 13:46 ` Kevin Wolf [this message]
2010-05-27 14:12 ` Stefan Hajnoczi
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=4BFE77BE.4040808@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).