From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Stephan Kulow" <coolo@suse.de>,
"Andreas Färber" <afaerber@suse.de>,
"Bruce Rogers" <brogers@suse.com>
Subject: Re: [Qemu-devel] [PULL for-2.1 0/2] vnc: fix two vnc update issues.
Date: Fri, 25 Jul 2014 09:45:38 +0200 [thread overview]
Message-ID: <1406274338.20767.0.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <CAFEAcA9Qud0YyX_WUQrw7jtocabUYBZTR_fOL7Z6Ycfnj8HCPQ@mail.gmail.com>
On Do, 2014-07-24 at 15:22 +0100, Peter Maydell wrote:
> On 24 July 2014 15:10, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > Hi,
> >
> >> > So are these *really* release critical bugs, if they've been
> >> > only found in code review? We're really close to release now
> >> > and so my preference is not to include changes unless they're
> >> > really necessary...
> >>
> >> These are fixing openQA breakage (os-autoinst),
> >
> > In more detail:
> > [snip]
>
> Thanks for the clarification; these do seem worth putting in 2.1.
> I'll need to get you to respin with the missing signed-off-by
> that Andreas pointed out, though.
Done: git://git.kraxel.org/qemu tags/pull-vnc-20140725-1
cheers,
Gerd
next prev parent reply other threads:[~2014-07-25 7:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 8:28 [Qemu-devel] [PULL for-2.1 0/2] vnc: fix two vnc update issues Gerd Hoffmann
2014-07-24 8:28 ` [Qemu-devel] [PULL for-2.1 1/2] fix full frame updates for VNC clients Gerd Hoffmann
2014-07-24 12:30 ` Andreas Färber
2014-07-24 13:45 ` Stephan Kulow
2014-07-24 13:57 ` Andreas Färber
2014-07-24 8:28 ` [Qemu-devel] [PULL for-2.1 2/2] vnc update fix Gerd Hoffmann
2014-07-24 11:48 ` [Qemu-devel] [PULL for-2.1 0/2] vnc: fix two vnc update issues Peter Maydell
2014-07-24 12:20 ` Andreas Färber
2014-07-24 14:10 ` Gerd Hoffmann
2014-07-24 14:22 ` Peter Maydell
2014-07-25 7:45 ` Gerd Hoffmann [this message]
2014-07-25 11:52 ` Peter Maydell
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=1406274338.20767.0.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=afaerber@suse.de \
--cc=brogers@suse.com \
--cc=coolo@suse.de \
--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).