Re: git commit <path> scanning entire working tree?

On Monday 16 February 2009 18:28:10 Junio C Hamano wrote:

skillzero@gmail.com writes:

quoted

When I do a 'git commit <path to a single file>', git seems to scan
the entire working tree.  [I]t takes quite a while (5 or so
seconds) before I can even edit the commit message.

Do you mean you edit the commit message, starting from the message
template "git commit" gives you?

The template lists "Changes to be committed", but
also "Changed but not updated" and "Untracked files".  You cannot generate
the latter two lists without checking with your work tree.

So, specify one or more -m options and you shouldn't see the scan.
-- 
Boyd Stephen Smith Jr.                   ,= ,-_-. =.
bss@iguanasuicide.net                   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy         `-'(. .)`-'
http://iguanasuicide.net/                    \_/