qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	Evgeny Voevodin <e.voevodin@samsung.com>,
	Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] checkpatch: Don't WARN about missing spaces in audio files
Date: Fri, 17 Feb 2012 09:26:53 -0600	[thread overview]
Message-ID: <4F3E71BD.6030506@us.ibm.com> (raw)
In-Reply-To: <m3sji9jyqu.fsf@blackfin.pond.sub.org>

On 02/17/2012 08:55 AM, Markus Armbruster wrote:
> Anthony Liguori<aliguori@us.ibm.com>  writes:
>
>> I really hate having these discussions.  I would almost rather we just
>> pay the one-time cost of re-indenting so we can stop debating about
>> this.
>>
>> For folks that feel strongly about this, please submit the following:
>>
>> An indent command that takes the tree to CODING_STYLE along with a
>> diffstat of the end result.
>>
>> Depending on how bad the diffstat is, we can consider doing this and
>> ending this set of arguments once and for all.
>
> The only justification for an idiosyncratic coding style I can buy is
> minimizing reindentation of old code.

Well this was what I was getting at in my previous comments.  If we just need to 
reindent < 10 files with a few random changes here and there, then maybe that 
isn't so bad.

But if we have to touch every single file in the tree in a significant way, then 
no way is it justified.

> If we reindent anyway, reindent
> to something that isn't specific to the QEMU island, please.

I don't even want to consider something that touches every line of code.  That's 
effectively creating a new source tree and losing the continuity of our SCM history.

Regards,

Anthony Liguori

  reply	other threads:[~2012-02-17 15:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 14:59 [Qemu-devel] [PATCH] checkpatch: Don't WARN about missing spaces in audio files Andreas Färber
2012-02-09 15:03 ` Andreas Färber
2012-02-09 16:43 ` malc
2012-02-10  3:50 ` Evgeny Voevodin
2012-02-10  4:02   ` malc
2012-02-10 17:47     ` Anthony Liguori
2012-02-11  9:44       ` Blue Swirl
2012-02-17 14:31         ` Anthony Liguori
2012-02-17 14:55           ` Markus Armbruster
2012-02-17 15:26             ` Anthony Liguori [this message]
2012-02-18  9:13               ` Blue Swirl
2012-02-18 10:56                 ` Stefan Weil
2012-02-18 14:18                   ` Anthony Liguori
2012-02-18 14:34                     ` Blue Swirl
2012-02-18 15:53                 ` Andreas Färber
2012-02-18 16:47                   ` Eric Blake
2012-02-18  8:56           ` Blue Swirl
2012-02-18  9:07             ` [Qemu-devel] [PATCH] astyle: Formatting rules for QEMU Stefan Weil
2012-02-18 10:10               ` Blue Swirl
2012-02-18 11:13                 ` Stefan Weil
2012-02-11  9:37 ` [Qemu-devel] [PATCH] checkpatch: Don't WARN about missing spaces in audio files Blue Swirl

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=4F3E71BD.6030506@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=e.voevodin@samsung.com \
    --cc=pbonzini@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).