From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: git-add has gone lstat() mad
Date: Fri, 30 Mar 2007 20:55:10 +0100 [thread overview]
Message-ID: <200703302055.13619.andyparkins@gmail.com> (raw)
Hello,
I was interested in trying out the GIT_WORK_DIR stuff, but ended up
being unable to. The thing that stopped me is present in master as
well:
$ git --version
git version 1.5.1.rc3.20.gaa453
$ cd $HOME
$ git init
$ git add .bashrc
At this point the CPU pegs at 100% systime. An strace shows that git is
calling lstat64() on every file in my home directory. I killed git
before it scanned everything I've ever done.
I only want to track one file; is git meant to scan every file in the
directory even though I'm not adding any of them?
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next reply other threads:[~2007-03-30 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 19:55 Andy Parkins [this message]
2007-03-30 20:20 ` git-add has gone lstat() mad Andy Parkins
2007-03-31 1:38 ` Junio C Hamano
2007-03-31 3:39 ` Linus Torvalds
2007-03-31 10:18 ` Andy Parkins
2007-03-31 14:54 ` Randal L. Schwartz
2007-03-31 15:09 ` Andy Parkins
2007-03-31 19:28 ` Tom Prince
2007-04-01 0:39 ` Junio C Hamano
2007-04-01 8:25 ` Andy Parkins
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=200703302055.13619.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@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).