From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org, lersek@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] less confusing block file names
Date: Thu, 27 Oct 2016 14:48:26 -0500 [thread overview]
Message-ID: <1477597708-3423-1-git-send-email-eblake@redhat.com> (raw)
Based on a suggestion here:
https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg00350.html
v1 was here, and got some R-b but also some discussion:
https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg04618.html
Since then:
patch 1: pick different filename and overhaul commit message, no
R-b applied
patch 2: minor merge context conflict due to patch 1, but R-b applies
Eric Blake (2):
block: Rename raw_bsd to raw-format.c
block: rename raw-{posix,win32} to file-*.c
include/block/block_int.h | 2 +-
block/{raw-posix.c => file-posix.c} | 0
block/{raw-win32.c => file-win32.c} | 0
block/gluster.c | 4 ++--
block/{raw_bsd.c => raw-format.c} | 2 +-
MAINTAINERS | 6 +++---
block/Makefile.objs | 6 +++---
block/trace-events | 4 ++--
configure | 2 +-
9 files changed, 13 insertions(+), 13 deletions(-)
rename block/{raw-posix.c => file-posix.c} (100%)
rename block/{raw-win32.c => file-win32.c} (100%)
rename block/{raw_bsd.c => raw-format.c} (99%)
--
2.7.4
next reply other threads:[~2016-10-27 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 19:48 Eric Blake [this message]
2016-10-27 19:48 ` [Qemu-devel] [PATCH v2 1/2] block: Rename raw_bsd to raw-format.c Eric Blake
2016-10-27 19:48 ` [Qemu-devel] [PATCH v2 2/2] block: rename raw-{posix, win32} to file-*.c Eric Blake
2016-10-28 9:59 ` [Qemu-devel] [PATCH v2 0/2] less confusing block file names Laszlo Ersek
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=1477597708-3423-1-git-send-email-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=lersek@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).