From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/2] less confusing block file names
Date: Tue, 13 Dec 2016 17:15:54 +0100 [thread overview]
Message-ID: <20161213161554.GB3918@noname.redhat.com> (raw)
In-Reply-To: <20161202194854.18737-1-eblake@redhat.com>
Am 02.12.2016 um 20:48 hat Eric Blake geschrieben:
> no real change from v2 other than trivial rebasing and R-by:
> https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg07220.html
>
> but it's been more than a month since the last activity, and the
> start of the release cycle is as good a time as any to avoid any
> potential churn on conflicts due to renaming files
>
> applies on Kevin's block-next branch for 2.9
Thanks, applied to block-next.
Kevin
prev parent reply other threads:[~2016-12-13 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 19:48 [Qemu-devel] [PATCH v3 0/2] less confusing block file names Eric Blake
2016-12-02 19:48 ` [Qemu-devel] [PATCH v3 1/2] block: Rename raw_bsd to raw-format.c Eric Blake
2016-12-02 19:48 ` [Qemu-devel] [PATCH v3 2/2] block: Rename raw-{posix, win32} to file-*.c Eric Blake
2016-12-05 10:37 ` [Qemu-devel] [Qemu-block] [PATCH v3 0/2] less confusing block file names Stefan Hajnoczi
2016-12-13 16:15 ` Kevin Wolf [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=20161213161554.GB3918@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-block@nongnu.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).