From: Thomas Huth <thuth@redhat.com>
To: "Greg Kurz" <groug@kaod.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: pbonzini@redhat.com,
"Dr. David Alan Gilbert \(git\)" <dgilbert@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] ci: Use libcap-ng
Date: Mon, 2 Dec 2019 11:44:39 +0100 [thread overview]
Message-ID: <87c87c3c-d215-e380-3ac3-b43125f5ffa7@redhat.com> (raw)
In-Reply-To: <20191202114125.2ab5783d@bahia.w3ibm.bluemix.net>
On 02/12/2019 11.41, Greg Kurz wrote:
> On Fri, 29 Nov 2019 16:51:29 +0100
> Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>
>> On 11/29/19 3:21 PM, Dr. David Alan Gilbert (git) wrote:
>>> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>>>
>>> We currently enable libcap-dev in build-clang to pick up the 9p proxy
>>> helper. Paolo's patch changes that to use libcap-ng, so switch to using
>>
>> It is not obvious you are referring to "virtfs-proxy-helper: switch from
>> libcap to libcap-ng" he recently posted.
>>
>> Since Greg is going to take Paolo's patch, I'd suggest he also takes
>> this one, so he can update the commit description with either "the
>> previous patch" or the commit sha1.
>>
>
> I'm okay to take this one and to adapt the changelog if I get an ack from
> Thomas.
Feel free to recycle my Ack from here:
https://lists.gnu.org/archive/html/qemu-devel/2019-11/msg05178.html
Cheers,
Thomas
prev parent reply other threads:[~2019-12-02 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 14:21 [PATCH] ci: Use libcap-ng Dr. David Alan Gilbert (git)
2019-11-29 14:35 ` Thomas Huth
2019-11-29 14:46 ` Daniel P. Berrangé
2019-11-29 15:51 ` Philippe Mathieu-Daudé
2019-11-29 15:51 ` Philippe Mathieu-Daudé
2019-12-02 10:41 ` Greg Kurz
2019-12-02 10:44 ` Thomas Huth [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=87c87c3c-d215-e380-3ac3-b43125f5ffa7@redhat.com \
--to=thuth@redhat.com \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=pbonzini@redhat.com \
--cc=philmd@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 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).