[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F5B364A.5000209@gmail.com>
Date: Sat, 10 Mar 2012 13:08:58 +0200
From: Rares Aioanei <krnl.list@...il.com>
To: Prasanna Kumar T S M <prasannatsmkumar@...il.com>
CC: linux-kernel@...r.kernel.org
Subject: Re: Git pull on linux-next tree shows "Performing inexact rename
detection"
On 03/09/2012 08:28 PM, Prasanna Kumar T S M wrote:
> Doing "git pull" on linux-next tree always shows "Performing inexact
> rename detection" for a very long time (more than a hour and going). It
> also uses more than 1.5GB of RAM (out of 2GB RAM) in my system. Not able
> to do any thing when this is happening - even maximising a window takes
> 2 minutes once such a situation is reached. I am killing the command
> with a Ctrl + C as I am not able to do any work.
>
> What is the reason for this? What it does internally? Is there any way
> to circumvent this? I don't want to clone linux-next again (that seems
> to be the worst case solution).
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
The first Google search result gave me this:
http://git.661346.n2.nabble.com/Merging-limitations-after-directory-renames-interesting-test-repo-td6041103.html
While long and pretty technical, it will shed some light, I believe.
Good luck.
--
--
Rares Aioanei
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists