From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
libvir-list@redhat.com, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] ui: support for authorization control on TLS connections
Date: Thu, 7 Mar 2019 13:32:13 +0000 [thread overview]
Message-ID: <20190307133213.GC32268@redhat.com> (raw)
In-Reply-To: <20190307132730.trnlurxyuvptywcu@sirius.home.kraxel.org>
On Thu, Mar 07, 2019 at 02:27:30PM +0100, Gerd Hoffmann wrote:
> On Thu, Mar 07, 2019 at 12:23:58PM +0000, Daniel P. Berrangé wrote:
> > ping - soft freeze is less than a week away & i'd like this to get into
> > a ui queue pull request in time for 4.0 if there's no review objections
>
> I'm aware, I'm busy preparing the pre-freeze pulls. USB is on the list
> already, busy with UI right now. VGA comes next.
>
> Series queued.
Thanks for the quick reply !
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 :|
prev parent reply other threads:[~2019-03-07 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 14:57 [Qemu-devel] [PATCH 0/2] ui: support for authorization control on TLS connections Daniel P. Berrangé
2019-02-27 14:57 ` [Qemu-devel] [PATCH 1/2] vnc: allow specifying a custom authorization object name Daniel P. Berrangé
2019-02-27 14:57 ` [Qemu-devel] [PATCH 2/2] monitor: deprecate acl_show, acl_reset, acl_policy, acl_add, acl_remove Daniel P. Berrangé
2019-03-07 12:23 ` [Qemu-devel] [PATCH 0/2] ui: support for authorization control on TLS connections Daniel P. Berrangé
2019-03-07 13:27 ` Gerd Hoffmann
2019-03-07 13:32 ` Daniel P. Berrangé [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=20190307133213.GC32268@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=libvir-list@redhat.com \
--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.