From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/7] powerpc/82xx: merge mgcoge.h and mgcoge3ne.h into km82xx.h
Date: Mon, 30 Jul 2012 18:07:53 +0200 [thread overview]
Message-ID: <20120730160753.900A720226A@gemini.denx.de> (raw)
In-Reply-To: <5016A093.6040102@keymile.com>
Dear Gerlando Falauto,
In message <5016A093.6040102@keymile.com> you wrote:
>
> The way I understand it, such renaming information is built on the fly
> while building the patch (like you're suggesting, it's a parameter to
> git format-patch, not to the commit itself).
Yes, and I fail to understand where your problems could be.
> However, I've been struggling to get this same kind of message through
> git-format-patch. No way, I don't know why. I tried with -M, -M -C,
> -M10%, adding "[diff]\n renames = copies" to ~/.gitconfig, with both
> versions below, nothing. Detected as a rename at commit time, it's a
> plain delete/create commit at patch creation time.
I see this (doing it all manually for testing):
-> patch -p1 </tmp/patch
-> git rm include/configs/mgcoge.h include/configs/mgcoge3ne.h
-> git add include/configs/km82xx.h
-> git commit -s -m 'test 1'
-> git format-patch -M -C --stdout HEAD^ >/tmp/patch
-> less /tmp/patch
next prev parent reply other threads:[~2012-07-30 16:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 15:16 [U-Boot] [PATCH 0/7] km82xx and mgcogeXxx reworking Gerlando Falauto
2012-07-27 15:16 ` [U-Boot] [PATCH 1/7] powerpc/82xx: remove unused define for mgcoge3ne Gerlando Falauto
2012-07-31 20:29 ` Wolfgang Denk
2012-07-27 15:16 ` [U-Boot] [PATCH 2/7] powerpc/82xx: move mgcoge, mgcoge3ne defines to ease subsequent merge Gerlando Falauto
2012-07-31 20:30 ` Wolfgang Denk
2012-08-02 9:14 ` [U-Boot] [PATCH v2 4/7] powerpc/82xx: move km/km82xx-common.h within km82xx.h Gerlando Falauto
2012-07-27 15:16 ` [U-Boot] [PATCH 3/7] powerpc/82xx: merge mgcoge.h and mgcoge3ne.h into km82xx.h Gerlando Falauto
2012-07-27 17:30 ` Wolfgang Denk
2012-07-30 9:09 ` Gerlando Falauto
2012-07-30 13:00 ` Wolfgang Denk
2012-07-30 14:56 ` Gerlando Falauto
2012-07-30 16:07 ` Wolfgang Denk [this message]
2012-07-30 18:21 ` Gerlando Falauto
2012-07-30 18:22 ` [U-Boot] [PATCH v2 " Gerlando Falauto
2012-07-31 20:30 ` [U-Boot] [PATCH " Wolfgang Denk
2012-07-27 15:16 ` [U-Boot] [PATCH 4/7] powerpc/82xx: move km/km82xx-common.h within km82xx.h Gerlando Falauto
2012-07-27 17:31 ` Wolfgang Denk
2012-07-30 18:28 ` Gerlando Falauto
2012-07-30 19:12 ` Wolfgang Denk
2012-08-02 9:10 ` Gerlando Falauto
2012-07-31 20:31 ` Wolfgang Denk
2012-07-27 15:16 ` [U-Boot] [PATCH 5/7] powerpc/82xx: add SDRAM detection for km82xx Gerlando Falauto
2012-07-31 20:31 ` Wolfgang Denk
2012-07-27 15:16 ` [U-Boot] [PATCH 6/7] powerpc/82xx: use SDRAM detection for mgcoge2ne Gerlando Falauto
2012-07-31 20:31 ` Wolfgang Denk
2012-07-27 15:16 ` [U-Boot] [PATCH 7/7] powerpc/82xx: adapt SDRAM settings for mgcoge3ne Gerlando Falauto
2012-07-31 20:31 ` Wolfgang Denk
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=20120730160753.900A720226A@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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