From: Anthony Liguori <aliguori@us.ibm.com>
To: Glauber Costa <glommer@redhat.com>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT f80f9ec] Convert machine registration to use module initfunctions
Date: Thu, 21 May 2009 20:34:48 -0500 [thread overview]
Message-ID: <4A160138.7050109@us.ibm.com> (raw)
In-Reply-To: <20090521225039.GA26811@poweredge.glommer>
Glauber Costa wrote:
> On Thu, May 21, 2009 at 11:36:01PM +0100, Paul Brook wrote:
>
>>> From: Anthony Liguori <aliguori@us.ibm.com>
>>>
>>> This cleans up quite a lot of #ifdefs, extern variables, and other
>>> ugliness.
>>>
>> This changes the default for at least the ARM target, which I consider to be a
>> bug. Worse than that, the default is now arbitrary and depends on unspecified
>> toolchain implementation details.
>>
> How about we start sending patches to the list? Then this kind of thing can be avoided.
>
It doesn't magically solve the problem. I post most patches and still
regressions slip in. I review every patch I commit and still
regressions slip in. People are imperfect.
The best way to prevent regressions is to have an automated test suite
that everyone can use to validate that a series of patches doesn't break
things.
> Note that although at first there is nothing wrong with just messing around with
> the devel repository, this kind of thing breaks bisectability of the tree, which is kind
> of a pain.
>
You can always --skip. I understand your point. In this case, the
patch was very large and mostly mechanical. There was a design flaw but
I didn't expect to get much useful feedback because of the shear amount
of things it touched.
Regression tests are the only way we're going to really solve this problem.
--
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-05-22 1:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200905211348.n4LDmnYd025976@d01av04.pok.ibm.com>
2009-05-21 22:36 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT f80f9ec] Convert machine registration to use module initfunctions Paul Brook
2009-05-21 22:50 ` Glauber Costa
2009-05-22 1:34 ` Anthony Liguori [this message]
2009-05-22 1:49 ` Glauber Costa
2009-05-22 2:00 ` Anthony Liguori
2009-05-23 14:22 ` autotest (was Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT f80f9ec] Convert machine registration to use module initfunctions) Dor Laor
2009-05-24 19:46 ` Anthony Liguori
2009-05-24 20:50 ` Avi Kivity
2009-05-26 8:10 ` Anthony Liguori
2009-05-26 9:17 ` Avi Kivity
2009-05-26 9:17 ` Dor Laor
2009-05-26 9:30 ` Anthony Liguori
2009-05-26 9:54 ` Dor Laor
2009-05-22 1:21 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT f80f9ec] Convert machine registration to use module initfunctions Anthony Liguori
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=4A160138.7050109@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=glommer@redhat.com \
--cc=paul@codesourcery.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).