From: Greg Kurz <groug@kaod.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] travis.yml: Drop libcap-dev
Date: Wed, 4 Dec 2019 09:12:53 +0100 [thread overview]
Message-ID: <20191204091253.221cacbc@bahia.w3ibm.bluemix.net> (raw)
In-Reply-To: <69a9224c-4686-cd09-1a89-81954af6f902@redhat.com>
On Wed, 4 Dec 2019 09:07:42 +0100
Thomas Huth <thuth@redhat.com> wrote:
> On 04/12/2019 09.01, Greg Kurz wrote:
> > Commit b1553ab12fe0 converted virtfs-proxy-helper to using libcap-ng. There
> > aren't any users of libcap anymore. No need to install libcap-dev.
> >
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> >
> > Yet another follow-up to Paolo's patch to use libcap-ng instead of libcap.
> > Like with the docker and the gitlab CI patches, if I get an ack from Alex
> > I'll gladly merge this in the 9p tree and send a PR as soon as 5.0 dev
> > begins. I'll make sure the SHA1 for Paolo's patch remains the same.
>
> I hope you don't have to rebase! Otherwise simply say "One of the
> previous changes ..." or so in the commit message instead.
>
I don't expect to rebase, hence the SHA1.
> > .travis.yml | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/.travis.yml b/.travis.yml
> > index 445b0646c18a..6cb8af6fa599 100644
> > --- a/.travis.yml
> > +++ b/.travis.yml
> > @@ -26,7 +26,6 @@ addons:
> > - libaio-dev
> > - libattr1-dev
> > - libbrlapi-dev
> > - - libcap-dev
> > - libcap-ng-dev
> > - libgcc-4.8-dev
> > - libgnutls28-dev
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
>
Thanks.
next prev parent reply other threads:[~2019-12-04 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 8:01 [PATCH] travis.yml: Drop libcap-dev Greg Kurz
2019-12-04 8:07 ` Thomas Huth
2019-12-04 8:12 ` Greg Kurz [this message]
2019-12-04 9:33 ` Philippe Mathieu-Daudé
2019-12-04 13:49 ` Alex Bennée
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=20191204091253.221cacbc@bahia.w3ibm.bluemix.net \
--to=groug@kaod.org \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).