From: Kevin Wolf <kwolf@redhat.com>
To: Jean-Christophe Dubois <jcd@tribudubois.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix net.c coding style (with regard to tabs)
Date: Tue, 23 Jun 2009 10:09:35 +0200 [thread overview]
Message-ID: <4A408DBF.5010604@redhat.com> (raw)
In-Reply-To: <200906222046.41166.jcd@tribudubois.net>
Jean-Christophe Dubois schrieb:
> Le lundi 22 juin 2009 10:29:10 Kevin Wolf, vous avez écrit :
>> Jean-Christophe DUBOIS schrieb:
>>> This patch will replace existing tab in net.c with spaces
>>> in accordance with qemu CODING_STYLE.
>>>
>>> Note: This first patch is more of a test to see if it
>>> will be accepted and if it is worth spending my time on
>>> fixing the same issue in other files.
>>>
>>> Signed-off-by: Jean-Christophe DUBOIS <jcd@tribudubois.net>
>> I wouldn't do this. We should just pay attention to do it right in code
>> touched by new patches.
>
> Some people are speaking about not killing 2 birds with one stone (and I don't
> speak about the kitten ;-) ) and in general I would think you should fix one
> problem per patch. I am not sure it is a good idea to ask somebody fixing one
> line in a file to also fix all the coding style issues of this same file.
Agreed, this is obviously nonsense. I'm just talking about the lines
touched by the patch. What I mean is really just "Do it right in new
code, leave old code alone". You might argue that this results in files
with mixed indentation, but in my experience files using tabs are
already mixed in most cases.
Anyway, just my personal opinion and I'm not the one who's to decide if
we should have such whitespace cleanup patches.
Kevin
prev parent reply other threads:[~2009-06-23 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 21:22 [Qemu-devel] [PATCH] Fix net.c coding style (with regard to tabs) Jean-Christophe DUBOIS
2009-06-22 8:29 ` Kevin Wolf
2009-06-22 18:46 ` Jean-Christophe Dubois
2009-06-23 8:09 ` Kevin Wolf [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=4A408DBF.5010604@redhat.com \
--to=kwolf@redhat.com \
--cc=jcd@tribudubois.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).