git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 17, 2009, 07:12 UTC
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).

Previous: Boyd Stephen Smith Jr.Next: skillzero@gmail.com
Message 6 of 7 in “git commit <path> scanning entire working tree?”
  1. skillzero@gmail.comFeb 16, 2009
  2. Junio C HamanoFeb 17, 2009
  3. Boyd Stephen Smith Jr.Feb 17, 2009
  4. skillzero@gmail.comFeb 17, 2009
  5. Boyd Stephen Smith Jr.Feb 17, 2009
  6. Junio C HamanoFeb 17, 2009
  7. skillzero@gmail.comFeb 18, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.