From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [libvirt] [PULL 0/5] Ui 20190311 v2 patches
Date: Mon, 11 Mar 2019 14:12:28 +0000 [thread overview]
Message-ID: <20190311141228.GZ12393@redhat.com> (raw)
In-Reply-To: <20190311140816.gxveswhhzofwlgut@function>
On Mon, Mar 11, 2019 at 03:08:16PM +0100, Samuel Thibault wrote:
> Daniel P. Berrangé, le lun. 11 mars 2019 13:51:16 +0000, a ecrit:
> > On Mon, Mar 11, 2019 at 01:45:13PM +0000, Peter Maydell wrote:
> > > On Mon, 11 Mar 2019 at 08:40, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > > >
> > > > The following changes since commit e2a18635a400b0e68679614132e9ef6316105590:
> > > >
> > > > Merge remote-tracking branch 'remotes/ericb/tags/pull-nbd-2019-03-08' into staging (2019-03-09 20:55:44 +0000)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > > git://git.kraxel.org/qemu tags/ui-20190311-v2-pull-request
> > > >
> > > > for you to fetch changes up to 0143840771548e8ffece831398d745880ddfa080:
> > > >
> > > > monitor: deprecate acl_show, acl_reset, acl_policy, acl_add, acl_remove (2019-03-11 08:39:02 +0100)
> > > >
> > > > ----------------------------------------------------------------
> > > > curses: wide char input support.
> > > > vnc: acl update, stall fix.
> > > >
> > > > ----------------------------------------------------------------
> > >
> > > Applied, thanks.
> > >
> > > Please update the changelog at https://wiki.qemu.org/ChangeLog/4.0
> > > for any user-visible changes.
> >
> > Gerd, I'll take care of updating the changelog for the auth / acl
> > related parts of the pull request
>
> I wanted to do the same for the curses part but I don't seem to have a
> wiki account, could somebody create one for me?
Sure, I can create you an account. Will message you offlist...
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-03-11 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 8:26 [Qemu-devel] [PULL 0/5] Ui 20190311 v2 patches Gerd Hoffmann
2019-03-11 8:26 ` [Qemu-devel] [PULL 1/5] Reduce curses escdelay from 1s to 25ms Gerd Hoffmann
2019-03-11 8:26 ` [Qemu-devel] [PULL 2/5] curses: support wide input Gerd Hoffmann
2019-03-11 8:26 ` [Qemu-devel] [PULL 3/5] vnc: fix update stalls Gerd Hoffmann
2019-03-11 8:26 ` [Qemu-devel] [PULL 4/5] vnc: allow specifying a custom authorization object name Gerd Hoffmann
2019-03-11 8:26 ` [Qemu-devel] [PULL 5/5] monitor: deprecate acl_show, acl_reset, acl_policy, acl_add, acl_remove Gerd Hoffmann
2019-03-11 13:45 ` [Qemu-devel] [PULL 0/5] Ui 20190311 v2 patches Peter Maydell
2019-03-11 13:51 ` [Qemu-devel] [libvirt] " Daniel P. Berrangé
2019-03-11 14:08 ` Samuel Thibault
2019-03-11 14:12 ` Daniel P. Berrangé [this message]
2019-03-11 14:22 ` Samuel Thibault
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=20190311141228.GZ12393@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.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).