From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] scripts: provide a script for checking glib symbol usage
Date: Fri, 18 Dec 2015 14:49:31 +0000 [thread overview]
Message-ID: <20151218144931.GD7228@redhat.com> (raw)
In-Reply-To: <CAFEAcA8PoW_AfChZszKbiJHvmggBPPdxf7iYOeZMgxs9iOFcVA@mail.gmail.com>
On Fri, Dec 18, 2015 at 01:43:19PM +0000, Peter Maydell wrote:
> On 18 December 2015 at 13:41, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> >
> > On 18/12/2015 14:35, Dr. David Alan Gilbert wrote:
> >> > That would not be recursive make, but rather a completely separate
> >> > Makefile to be manually invoked with -f.
> >>
> >> Hmm but wouldn't this Makefile also be a good place for small-fast
> >> style check scripts that could be included in make check ?
> >
> > Yes, but there is no benefit from inclusion, since these tests do not
> > depend on anything having been built already.
>
> In particular, if it doesn't require a preceding configure or
> build I can just run it once as part of my merge testing rather
> than farming it out to be run in parallel on five machines and
> ten different configs :-)
Ok, yeah, that makes total sense - it certainly shouldn't depend on
any configure / build step.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2015-12-18 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 11:36 [Qemu-devel] [PATCH] scripts: provide a script for checking glib symbol usage Daniel P. Berrange
2015-12-18 12:36 ` Paolo Bonzini
2015-12-18 13:05 ` Daniel P. Berrange
2015-12-18 13:08 ` Paolo Bonzini
2015-12-18 13:35 ` Dr. David Alan Gilbert
2015-12-18 13:37 ` Daniel P. Berrange
2015-12-18 13:42 ` Dr. David Alan Gilbert
2015-12-18 13:49 ` Peter Maydell
2015-12-18 13:52 ` Dr. David Alan Gilbert
2015-12-18 13:41 ` Paolo Bonzini
2015-12-18 13:43 ` Peter Maydell
2015-12-18 14:49 ` Daniel P. Berrange [this message]
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=20151218144931.GD7228@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).