linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prasanna Kumar T S M <prasannatsmkumar@gmail.com>
To: Rares Aioanei <krnl.list@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Git pull on linux-next tree shows "Performing inexact rename detection"
Date: Sat, 10 Mar 2012 21:51:30 +0530	[thread overview]
Message-ID: <4F5B7F8A.1040000@gmail.com> (raw)
In-Reply-To: <4F5B364A.5000209@gmail.com>

On Saturday 10 March 2012 04:38 PM, Rares Aioanei wrote:

> 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@vger.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.
> 


As mentioned in the thread it uses up all my RAM and also does a lot of
paging. In such situations I am not able to use the system. The big
issue is that it takes a very long time (I have waited for 1 hour and
more yet it did not stop). Is there any short cut route to pull the code?

Thanks,
PrasannaKumar

  reply	other threads:[~2012-03-10 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 18:28 Git pull on linux-next tree shows "Performing inexact rename detection" Prasanna Kumar T S M
2012-03-10 11:08 ` Rares Aioanei
2012-03-10 16:21   ` Prasanna Kumar T S M [this message]
2012-03-10 18:46 ` Geert Uytterhoeven

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=4F5B7F8A.1040000@gmail.com \
    --to=prasannatsmkumar@gmail.com \
    --cc=krnl.list@gmail.com \
    --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).