qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Glauber Costa <glommer@gmail.com>
Cc: qemu-devel@nongnu.org, Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Subject: Re: [Qemu-devel] [7234] Use a more natural order
Date: Thu, 23 Apr 2009 22:39:29 +0300	[thread overview]
Message-ID: <f43fc5580904231239o213a4e2dl4cc5250ab8f55bd2@mail.gmail.com> (raw)
In-Reply-To: <5d6222a80904231215p62c6594asc50230b252e892aa@mail.gmail.com>

On 4/23/09, Glauber Costa <glommer@gmail.com> wrote:
> On Thu, Apr 23, 2009 at 4:10 PM, Lennart Sorensen
>
> <lsorense@csclub.uwaterloo.ca> wrote:
>
> > On Thu, Apr 23, 2009 at 10:01:43PM +0300, Blue Swirl wrote:
>  >> True, but it's not the style that is used here. You are of course free
>  >> to argue for using this version and even submit patches.
>  >
>  > I didn't check if it is covered by the codestyle or not for qemu.
>  >
>  > If your patch comment had said "Fix to follow code style" rather than
>  > "make natural order" I wouldn't have said anything.  Natural order in
>  > this case is a bad reason for the change.  Following code style is a
>  > good reason (even if the code style may then be questionable).
>  >
>  > If the code style doesn't cover it at all, I would say the change is
>  > horrible and shouldn't be done at all.  The change even caused a compile
>  > failure briefly (and hence breaks git bisect) by being commited completely
>  > untested I suspect.  If it didn't cause a compile failure it at least
>  > should have caused a serious warning.
>
>
> Note that this could be avoided by not commiting the code in the first place,
>  but rather, sending it to the mailing list. Everybody should be sending code
>  to the mailing list, even maintainers.
>
>  Anthony is already doing that, and it greatly reduces the probability of getting
>  a broken bisect for broken patches.

In this case he committed the patches even though I had pointed out
these few remaining instances of this style. Gerd had fixed most of
the issues on previous rounds but some were still left.

  reply	other threads:[~2009-04-23 19:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 18:29 [Qemu-devel] [7234] Use a more natural order Blue Swirl
2009-04-23 18:39 ` Andreas Färber
2009-04-23 18:43   ` Blue Swirl
2009-04-23 18:53 ` Lennart Sorensen
2009-04-23 19:01   ` Blue Swirl
2009-04-23 19:10     ` Lennart Sorensen
2009-04-23 19:15       ` Glauber Costa
2009-04-23 19:39         ` Blue Swirl [this message]
2009-04-23 19:59           ` Anthony Liguori
2009-04-23 20:20             ` Blue Swirl
2009-04-23 19:57         ` Anthony Liguori
2009-04-23 19:59           ` Lennart Sorensen
2009-04-23 20:03             ` Anthony Liguori
2009-04-23 20:54               ` Lennart Sorensen
2009-04-23 21:15                 ` Anthony Liguori
2009-04-23 22:13                   ` Jamie Lokier
2009-04-24  0:10                     ` Anthony Liguori
2009-04-24  8:18                 ` Gerd Hoffmann
2009-04-24 12:14                   ` Anthony Liguori
2009-04-24 12:32                   ` Stefan Weil
2009-04-23 19:31       ` Blue Swirl
2009-04-23 19:44         ` Lennart Sorensen
2009-04-23 22:46           ` Jamie Lokier
2009-04-24 18:07             ` Lennart Sorensen
2009-04-24 18:58               ` Nathan Froyd
2009-04-23 19:12   ` M. Warner Losh
2009-04-23 19:28     ` Lennart Sorensen
2009-04-23 19:41       ` M. Warner Losh
2009-04-23 19:55         ` Lennart Sorensen
2009-04-23 20:07           ` M. Warner Losh
2009-04-23 21:01             ` Lennart Sorensen
2009-04-23 23:02           ` Jamie Lokier
2009-04-23 22:52       ` Jamie Lokier
2009-04-23 19:37   ` [Qemu-devel] " Jan Kiszka
2009-04-23 19:46     ` Lennart Sorensen
2009-04-23 21:30       ` malc
2009-04-23 22:10       ` Jamie Lokier
2009-04-24  8:09   ` [Qemu-devel] " Gerd Hoffmann

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=f43fc5580904231239o213a4e2dl4cc5250ab8f55bd2@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=glommer@gmail.com \
    --cc=lsorense@csclub.uwaterloo.ca \
    --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).