On Jul 2, 5:17 pm, Thomas Ferris Nicolaisen <tfn...@gmail.com> wrote:
> On Monday, July 2, 2012 6:40:02 AM UTC+2, jack sparrow wrote:
> > i tried with git version 184.108.40.206, the issue still remains,
> > this is a build repo from my organisation,
> > unfortunately i can't replicate the build
> > with that many files. GIT_TRACE is not helping
> > either, it just throws the following line.
> > trace: built-in: git 'status'
> > are there any verbose debugs that i can enable during
> > compliation ?
> Not that I know about. You have to take the problem to the Git development
> mailing list g...@vger.kernel.org described onhttp://git-scm.com/community
> I do know that on encrypted disks, Git's performance can suffer. Also if
> you have a disk that has anything less than 5400 RPMs, or if you use some
> sort of exotic filesystem that Git isn't optimized for, Git will be slow.
> You can see if the problems are caused by the long history in your project
> by initializing the source code in a fresh repo like this:
> git clone old-repo new-repo
> cd new-repo
> rm -rf .git
> git init
> git add .
> git commit -m "Initial commit in a repo just to see if it makes a
> git status #benchmark
I've done the above, it still is taking long time. I guess i have no
way but to live with it.
btw, what's the command to display the statistics like the number of
no.of files in the repo etc ?
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at