From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Eric Blake <eblake@redhat.com>, qemu-ppc@nongnu.org
Cc: david@gibson.dropbear.id.au, qemu-devel@nongnu.org,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] ppc: Rename #include'd .c files to .inc.c
Date: Sat, 06 Aug 2016 08:40:40 +1000 [thread overview]
Message-ID: <1470436840.12584.167.camel@kernel.crashing.org> (raw)
In-Reply-To: <57A4CDA8.7050001@redhat.com>
On Fri, 2016-08-05 at 11:32 -0600, Eric Blake wrote:
> Per http://wiki.qemu.org/Contribute/SubmitAPatch, if you would do:
>
> git config diff.renames true
>
> then your email would be MUCH smaller, calling our attention to what
> changed to accommodate the rename rather than treating the entire
> file as deleted than new contents.
Just an oversight, I had it configured properly on another machine. The
subsequent submission of that patch was correct.
prev parent reply other threads:[~2016-08-05 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 22:30 [Qemu-devel] [PATCH] ppc: Rename #include'd .c files to .inc.c Benjamin Herrenschmidt
2016-07-29 4:37 ` David Gibson
2016-08-05 17:32 ` Eric Blake
2016-08-05 22:40 ` Benjamin Herrenschmidt [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=1470436840.12584.167.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rth@twiddle.net \
/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).