From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Eric Blake <eblake@redhat.com>
Cc: berrange@redhat.com, qemu-block@nongnu.org, armbru@redhat.com,
qemu-devel@nongnu.org, stefanha@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] less confusing block file names
Date: Mon, 24 Oct 2016 16:44:33 +0200 [thread overview]
Message-ID: <b5c06bd6-7ad4-c2d0-d114-bf7c0bcce65d@redhat.com> (raw)
In-Reply-To: <20161024134750.GC4374@noname.redhat.com>
On 24/10/2016 15:47, Kevin Wolf wrote:
> One effect that makes me less than fully happy is that 'git log
> block/raw.c' without --follow mixes the history of the renamed driver
> with the history of the old, differently licensed one. On the other
> hand, the removal of the old driver happened three years ago, so it's
> probably unlikely that people confuse what belongs to which one and
> revive old code accidentally.
Hmm, this makes it sensible to only apply patch 2, especially since Eric
has corteously split them. :)
Paolo
next prev parent reply other threads:[~2016-10-24 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 1:11 [Qemu-devel] [PATCH 0/2] less confusing block file names Eric Blake
2016-10-20 1:11 ` [Qemu-devel] [PATCH 1/2] block: Rename raw_bsd to raw.c Eric Blake
2016-10-24 14:54 ` Laszlo Ersek
2016-10-20 1:11 ` [Qemu-devel] [PATCH 2/2] block: rename raw-{posix, win32} to file-*.c Eric Blake
2016-10-24 14:56 ` Laszlo Ersek
2016-10-21 20:17 ` [Qemu-devel] [Qemu-block] [PATCH 0/2] less confusing block file names John Snow
2016-10-24 13:47 ` [Qemu-devel] " Kevin Wolf
2016-10-24 14:44 ` Paolo Bonzini [this message]
2016-10-24 15:14 ` Kevin Wolf
2016-10-24 19:47 ` Eric Blake
2016-10-24 15:44 ` Eric Blake
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=b5c06bd6-7ad4-c2d0-d114-bf7c0bcce65d@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).