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

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

From
Sskillzero@gmail.com <skillzero@gmail.com>
Date
Feb 18, 2009, 02:25 UTC
Message-ID
<2729632a0902171825g2078755cx6b966417240a59ca@mail.gmail.com>
In-Reply-To
<7vvdr98rkd.fsf@gitster.siamese.dyndns.org>
On Mon, Feb 16, 2009 at 11:12 PM, Junio C Hamano <gitster@pobox.com> wrote:
> skillzero@gmail.com writes:
> People do rely on that information.  Why else we would spend cycles to show
> them?

My guess was that most people didn't work with very large trees. For example, the Linux kernel tree stat's pretty quickly (.7 seconds when hot on my machine), but my tree contains the code for an entire OS distribution so even on a fast machine and OS, it takes many seconds.

My thinking was that in the case when a path was specified, people might be less interested in changes/untracked files outside that path (although I may be totally wrong). If a path wasn't specified, I can see why it would be useful to show everything. I tend to do a 'git status' then a bunch of 'git commit <path>' commands.

> 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).

Thanks, I'll check it out. If that doesn't do what I need, maybe I can trying changing git to add support for automatically skipping files outside the specifies path and submit a patch for you guys to rip to shreds :)

Previous: Junio C Hamano
Message 7 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.