git commit <path> scanning entire working tree?
- From
- skillzero@gmail.com <skillzero@gmail.com>
- Date
- Feb 16, 2009, 22:58 UTC
- Message-ID
- <2729632a0902161458m732af362od59e5f35af5643c3@mail.gmail.com>
When I do a 'git commit <path to a single file>', git seems to scan the entire working tree. Since my tree is relatively large (and when on Windows, stat'ing is even slower), it takes quite a while (5 or so seconds) before I can even edit the commit message.
Is there a reason it needs to scan like this when the commit command specifies a specific path? It seems like it would only need to scan the path I've specified.