From: "Andreas Färber" <andreas.faerber@web.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] ui/cocoa.m: Update to new DisplayChangeListener member names
Date: Fri, 02 Nov 2012 16:44:52 +0100 [thread overview]
Message-ID: <5093EA74.8060904@web.de> (raw)
In-Reply-To: <5093E9C1.408@redhat.com>
Hi,
Am 02.11.2012 16:41, schrieb Gerd Hoffmann:
>> (I have a philosophical preference for compile fixes being applied
>> directly and quickly to master but my opinion on that matter is
>> not particularly significant :-))
>
> /me too. Build fixes should go in on the fast track. First because a
> broken build is annonying. Second because buildbots are less useful if
> builds are broken for longer periods.
Fine with me, less work. We should cc a maintainer then. ;)
> One of the reasons I didn't notice the xenfb breakage was because the
> fedora build is broken for other reasons, so the buildbot doesn't came
> to the point where it tries to build xenfb.c and figures it doesn't.
>
> Should we maybe agree on a special buildfix patch subject tag, so
> maintainers can easily filter and prioritize them?
I used [PATCH buildfix] or so in the past.
Regards,
Andreas
next prev parent reply other threads:[~2012-11-02 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 14:54 [Qemu-devel] [PATCH] ui/cocoa.m: Update to new DisplayChangeListener member names Peter Maydell
2012-11-02 14:59 ` Gerd Hoffmann
2012-11-02 15:04 ` Andreas Färber
2012-11-02 15:19 ` Peter Maydell
2012-11-02 15:41 ` Gerd Hoffmann
2012-11-02 15:44 ` Andreas Färber [this message]
2012-11-02 16:15 ` Anthony Liguori
2012-11-02 19:15 ` 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=5093EA74.8060904@web.de \
--to=andreas.faerber@web.de \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=patches@linaro.org \
--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).