From: Anthony Liguori <anthony@codemonkey.ws>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Glauber Costa <glommer@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [7234] Use a more natural order
Date: Thu, 23 Apr 2009 15:03:54 -0500 [thread overview]
Message-ID: <49F0C9AA.1070703@codemonkey.ws> (raw)
In-Reply-To: <20090423195902.GN3795@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
> On Thu, Apr 23, 2009 at 02:57:26PM -0500, Anthony Liguori wrote:
>
>> In all fairness, I usually only do that when it's something I think
>> people would comment on. I probably would do a fix up like this by just
>> committing.
>>
>> People miss things, it happens. No process is going to prevent it
>> happening 100% of the time.
>>
>
> If you can't bother to compile test it, you shouldn't be commiting.
> Your time isn't worth that much more than everyone else that gets
> inconvinienced by the sloppy commit.
>
> That's a procedure that can certainly help.
>
I was obviously referring to posting to the mailing list. I have a set
of compilation and unit tests that get run before every commit.
There are a lot of possible configuration options for QEMU. Sometimes
the build breaks for some combination of configuration options and this
is a difficult thing to address in a robust way. With a patch series,
my scripts run through what I consider the most common set of
configurations for each patch. Right now, it usually takes a good 30
minutes to go through a large series just to compile test with my
default configurations.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-04-23 20:04 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
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 [this message]
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=49F0C9AA.1070703@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.