From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Olof Johannsson <olof@lixom.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/pasemi: Only the build the pasemi MSI code for PASEMI=y
Date: Sun, 12 Apr 2015 14:04:09 -0500 [thread overview]
Message-ID: <20150412190409.GA16978@gate.crashing.org> (raw)
In-Reply-To: <1428662335.21137.1.camel@ellerman.id.au>
On Fri, Apr 10, 2015 at 08:38:55PM +1000, Michael Ellerman wrote:
> BUT, I can't work out how to tell git-send-email I *always* want to pass -M, so
> I'll probably forget next time :)
In your config:
--
[diff]
renames = true
--
but this will do it for all diffs, not just for format-patch.
Segher
next prev parent reply other threads:[~2015-04-12 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 1:52 [PATCH] powerpc/pasemi: Only the build the pasemi MSI code for PASEMI=y Michael Ellerman
2015-04-10 4:24 ` Stephen Rothwell
2015-04-10 5:28 ` Michael Ellerman
2015-04-10 6:42 ` Stephen Rothwell
2015-04-10 10:38 ` Michael Ellerman
2015-04-12 19:04 ` Segher Boessenkool [this message]
2015-04-13 1:03 ` Michael Ellerman
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=20150412190409.GA16978@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
/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).