From: Kashyap Chamarthy <kchamart@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, kwolf@redhat.com,
mreitz@redhat.com, jsnow@redhat.com, berto@igalia.com
Subject: Re: [Qemu-devel] [PATCH v6 1/2] bitmaps.md: Convert to rST; move it into 'interop' dir
Date: Tue, 11 Jul 2017 13:49:51 +0200 [thread overview]
Message-ID: <20170711114951.bzxzkwajvbhjs4z2@eukaryote> (raw)
In-Reply-To: <5215f15d-9d8b-698f-30a0-b2f569cbc59a@redhat.com>
On Tue, Jul 11, 2017 at 06:33:22AM -0500, Eric Blake wrote:
> On 07/11/2017 02:58 AM, Kashyap Chamarthy wrote:
[...]
> >> A shame that git rename detection doesn't see these as the same rough
> >> contents, but not too bad.
> >
> > _Should_ it detect?
>
> It depends on the similarities between the file, and on whether you have
> 'git config diff.renames true' set (there are some other parameters you
> can set to fine-tune how much effort git expends on detecting file
> renames, but the defaults are usually good enough).
I see, noted.
[...]
> > Indeed -- the things you point out further below were already
> > pre-existing.
> >
> > Asking out of curiosity: You say it is nicer split because we'll retain
> > the `git-bisect`-ability? Or just to keep text motion and actual
> > changes separate? (I think both.)
>
> bisect-ability is important on code, but less so on docs. If you were
> doing code motion, I'd absolutely insist that cleanups be separate from
> the motion; but here I don't have a strong preference (separating the
> cleanups DOES make it easier to perform a backport of the cleanup
> without having to backport the rename, but backporting docs tends to be
> less of a priority than backporting code functionality).
Yep, fully agree with you, and I guessed as much. Given this
understanding, I'll just fix your feedback in this series.
Thanks.
--
/kashyap
next prev parent reply other threads:[~2017-07-11 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 8:15 [Qemu-devel] [PATCH v6 0/2] Rewrite 'live-block-ops.txt'; convert 'bitmaps.md' to rST Kashyap Chamarthy
2017-07-10 8:15 ` [Qemu-devel] [PATCH v6 1/2] bitmaps.md: Convert to rST; move it into 'interop' dir Kashyap Chamarthy
2017-07-11 2:36 ` Eric Blake
2017-07-11 7:58 ` Kashyap Chamarthy
2017-07-11 11:33 ` Eric Blake
2017-07-11 11:49 ` Kashyap Chamarthy [this message]
2017-07-11 16:11 ` John Snow
2017-07-10 8:15 ` [Qemu-devel] [PATCH v6 2/2] live-block-ops.txt: Rename, rewrite, and improve it Kashyap Chamarthy
2017-07-11 15:03 ` Eric Blake
2017-07-17 9:14 ` Kashyap Chamarthy
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=20170711114951.bzxzkwajvbhjs4z2@eukaryote \
--to=kchamart@redhat.com \
--cc=berto@igalia.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).