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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



skillzero@xxxxxxxxx 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).
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux