From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] CODING_STYLE: {} as in linux kernel
Date: Tue, 6 Oct 2009 22:41:20 +0100 [thread overview]
Message-ID: <20091006214120.GA31403@miranda.arrow> (raw)
In-Reply-To: <20091006190115.GA4768@redhat.com>
On Tue, Oct 06, 2009 at 09:01:15PM +0200, Michael S. Tsirkin wrote:
> Most people seem to hate using {} around sngle-statement blocks.
> And code isn't consistent either way. So let's change our standard
> to something most people like, and eliminate the pain source.
I can't see how this is really an improvement. All it means is
that patches have to deal with adding extra '{'s and '}'s, which
is a pointless distraction when reading patches...
Regards,
--
Stuart Brady
next prev parent reply other threads:[~2009-10-06 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 19:01 [Qemu-devel] [PATCH] CODING_STYLE: {} as in linux kernel Michael S. Tsirkin
2009-10-06 21:08 ` Stefan Weil
2009-10-06 21:43 ` Anthony Liguori
2009-10-07 12:59 ` Markus Armbruster
2009-10-06 21:41 ` Stuart Brady [this message]
2009-10-07 9:11 ` Jamie Lokier
2009-10-07 14:12 ` Kevin Wolf
2009-10-07 14:54 ` Gerd Hoffmann
2009-10-07 17:09 ` Stuart Brady
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=20091006214120.GA31403@miranda.arrow \
--to=sdbrady@ntlworld.com \
--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).