From: Peter Maydell <peter.maydell@linaro.org>
To: Greg Kurz <groug@kaod.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/5] 9pfs patches for QEMU 5.0
Date: Fri, 13 Dec 2019 15:58:28 +0000 [thread overview]
Message-ID: <CAFEAcA9mfqoKOtC6j9z62GauDyO2r2MZ=-vJ1dpE0W225HNnRw@mail.gmail.com> (raw)
In-Reply-To: <20191212223601.309245-1-groug@kaod.org>
On Thu, 12 Dec 2019 at 22:36, Greg Kurz <groug@kaod.org> wrote:
>
> The following changes since commit fb2246882a2c8d7f084ebe0617e97ac78467d156:
>
> .travis.yml: drop xcode9.4 from build matrix (2019-11-29 15:51:52 +0000)
>
> are available in the Git repository at:
>
> https://github.com/gkurz/qemu.git tags/9p-next-2019-12-12
>
> for you to fetch changes up to b3e2bb9458af556cb8aa0558f59222f462b81069:
>
> virtfs: Remove the deprecated "-virtfs_synth" option (2019-12-09 18:00:35 +0100)
>
> ----------------------------------------------------------------
> - conversion of virtfs-proxy-helper from libcap to libcap-ng
> - removal of libcap-dev from docker, travis and gitlab CI
> - removal of deprecate "-virtfs_synth" option
>
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/5.0
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2019-12-13 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 22:35 [PULL 0/5] 9pfs patches for QEMU 5.0 Greg Kurz
2019-12-12 22:35 ` [PULL 1/5] virtfs-proxy-helper: switch from libcap to libcap-ng Greg Kurz
2019-12-12 22:35 ` [PULL 2/5] docker: remove libcap development packages Greg Kurz
2019-12-12 22:35 ` [PULL 3/5] ci: Use libcap-ng Greg Kurz
2019-12-12 22:35 ` [PULL 4/5] travis.yml: Drop libcap-dev Greg Kurz
2019-12-12 22:36 ` [PULL 5/5] virtfs: Remove the deprecated "-virtfs_synth" option Greg Kurz
2019-12-13 15:58 ` Peter Maydell [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='CAFEAcA9mfqoKOtC6j9z62GauDyO2r2MZ=-vJ1dpE0W225HNnRw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=groug@kaod.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).