From: Prasanna Kumar T S M <prasannatsmkumar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Git pull on linux-next tree shows "Performing inexact rename detection"
Date: Fri, 09 Mar 2012 23:58:55 +0530 [thread overview]
Message-ID: <4F5A4BE7.60308@gmail.com> (raw)
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).
next reply other threads:[~2012-03-09 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 18:28 Prasanna Kumar T S M [this message]
2012-03-10 11:08 ` Git pull on linux-next tree shows "Performing inexact rename detection" Rares Aioanei
2012-03-10 16:21 ` Prasanna Kumar T S M
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=4F5A4BE7.60308@gmail.com \
--to=prasannatsmkumar@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).