linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, Olof Johansson <olof@lixom.net>,
	Russell King <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 05/11] SoC-level changes for tegra and omap
Date: Mon, 9 Jan 2012 14:37:17 -0800	[thread overview]
Message-ID: <CA+55aFyaOnJhrZOFnRiShH9kTeGEG8O8m9spvKF=c36QzjSvBA@mail.gmail.com> (raw)
In-Reply-To: <1326147171-13752-6-git-send-email-arnd@arndb.de>

On Mon, Jan 9, 2012 at 2:12 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>
>  58 files changed, 1967 insertions(+), 818 deletions(-)

Hmm. You don't seem to use the "detect renames" flag -M when you
create these, so the end result doesn't match mine.

With -M, it looks like this:

 54 files changed, 1399 insertions(+), 250 deletions(-)

because it sees these:

  rename arch/arm/mach-tegra/{board-dt.c => board-dt-tegra20.c} (91%)
  rename arch/arm/mach-tegra/include/mach/{pinmux-t2.h =>
pinmux-tegra20.h} (96%)
  rename arch/arm/mach-tegra/{pinmux-t2-tables.c =>
pinmux-tegra20-tables.c} (95%)
  rename arch/arm/plat-omap/include/plat/{ti816x.h => ti81xx.h} (60%)

Please do use -M, because it ends up making diffstats *so* much more
readable when there are renames (instead of big delete-create diffs,
you get a small diffstat that actually is much more relevant to what
happened).

                     Linus

  reply	other threads:[~2012-01-09 22:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 22:12 [GIT PULL 00/11] arm-soc changes Arnd Bergmann
2012-01-09 22:12 ` [GIT PULL 01/11] Non-critical bug fixes Arnd Bergmann
2012-01-09 22:12 ` [GIT PULL 02/11] Cleanups on various subarchitectures Arnd Bergmann
2012-01-09 22:12 ` [GIT PULL 03/11] Device tree conversions for samsung and tegra Arnd Bergmann
2012-01-09 22:12 ` [GIT PULL 04/11] Cleanups for the Samsung platforms Arnd Bergmann
2012-01-09 22:12 ` [GIT PULL 05/11] SoC-level changes for tegra and omap Arnd Bergmann
2012-01-09 22:37   ` Linus Torvalds [this message]
2012-01-10  8:39     ` Russell King - ARM Linux
2012-01-10 16:08       ` Linus Torvalds
2012-01-11  0:15         ` Junio C Hamano
2012-01-11 18:12           ` Arnd Bergmann
2012-01-11 20:29             ` Geert Uytterhoeven
2012-01-11 21:53               ` Nicolas Pitre
2012-01-11 23:21               ` Linus Torvalds
2012-01-12  6:32                 ` Geert Uytterhoeven
2012-01-12  6:41                   ` Linus Torvalds
2012-01-09 22:12 ` [GIT PULL 06/11] Board-level changes Arnd Bergmann
2012-01-09 22:12 ` [GIT PULL 07/11] New feature development Arnd Bergmann
2012-01-09 22:12 ` [GIT PULL 08/11] Driver specific changes Arnd Bergmann
2012-01-09 22:12 ` [GIT PULL 09/11] power management changes for omap and imx Arnd Bergmann
2012-01-09 22:12 ` [GIT PULL 10/11] timer changes for msm Arnd Bergmann
2012-01-09 22:12 ` [GIT PULL 11/11] clock management changes for i.MX Arnd Bergmann
2012-01-09 22:55 ` [GIT PULL 00/11] arm-soc changes Linus Torvalds

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='CA+55aFyaOnJhrZOFnRiShH9kTeGEG8O8m9spvKF=c36QzjSvBA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=olof@lixom.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).