linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Airlie <airlied@linux.ie>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm pull for 3.20-rc1
Date: Mon, 16 Feb 2015 16:07:26 -0800	[thread overview]
Message-ID: <CA+55aFyWefZ1jJLMJKXhy0Qif-iBmjG6n-evcbvkbWS5mDrs0g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1502160641200.2763@skynet.skynet.ie>

On Sun, Feb 15, 2015 at 10:43 PM, Dave Airlie <airlied@linux.ie> wrote:
>
> This is the main drm pull, it has a shared branch with some alsa crossover
> but everything should be acked by relevant people.

Ugh. Your diffstat is crap, because you don't show the inexact renames
that are very abundant in the nouveau driver.

The reason is likely that there are just so many renames that the
default git limits kick in, as it takes some amount of CPU and memory
to do well, and the git defaults are set to work on some really crappy
machines too.

Normally you don't hit the limits, because it's pretty unusual to see
that many renames, but the nouveau guys clearly reorganized their
whole subdirectory. And the difference is quite noticeable:

  # without inexact rename detection:
   1558 files changed, 141213 insertions(+), 125111 deletions(-)

  # with inexact rename detection:
   1138 files changed, 50782 insertions(+), 34680 deletions(-)

Git will actually warn you about a low renamelimit setting. So you
should have seen a warning something like

    warning: inexact rename detection was skipped due to too many files.
    warning: you may want to set your diff.renameLimit variable to at
least XYZ and retry the command.

but you might have overlooked it.

So may I ask you to just add

   [diff]
        renamelimit=0

to your ~/.gitconfig.  Or you can just do

    git config --global diff.renamelimit 0

to do it without editing it yourself, if that's what you prefer (the
"--global" just does it to your ~/.gitconfig so that it will affect
all your git projects - you can obviously just do it to the
".git/config" for individual repositories instead if you prefer).

Oh, and you can do it for merges too - just replace the "diff" with
"merge" - where it can arguably be even more important.

                     Linus

      reply	other threads:[~2015-02-17  0:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16  6:43 [git pull] drm pull for 3.20-rc1 Dave Airlie
2015-02-17  0:07 ` Linus Torvalds [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=CA+55aFyWefZ1jJLMJKXhy0Qif-iBmjG6n-evcbvkbWS5mDrs0g@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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).