From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 17 Feb 2009 07:12:50 GMT
Subject: Re: git commit <path> scanning entire working tree?
Message-ID: <7vvdr98rkd.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <2729632a0902161937o4ac3a1aeg143dda509ba5e384@mail.gmail.com>

skillzero@gmail.com writes:

> ... However, it would
> eliminate information (changed/untracked files outside that path), if
> people are relying on that.

People do rely on that information.  Why else we would spend cycles to show
them?

There is a precedence to allow a configuration variable to skip various
computation to help slow systems, e.g. 6c2ce04 (Add argument 'no'
commit/status option -u|--untracked-files, 2008-06-05).