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 17, 2009, 03:37 UTC
Message-ID
<2729632a0902161937o4ac3a1aeg143dda509ba5e384@mail.gmail.com>
In-Reply-To
<7vwsbpewkl.fsf@gitster.siamese.dyndns.org>
On Mon, Feb 16, 2009 at 4:28 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> Do you mean you edit the commit message, starting from the message
> template "git commit" gives you?

Yes, there's a large delay from me entering 'git commit -a' and when the editor shows up.

Show 6 quoted lines
> The template lists "Changes to be committed" (which obviously would list
> only the path that matches the single pathspec you give to the command,
> and there is no need to scan the whole tree -- it only needs to check the
> file or a directory hierarchy if the pathspec matches a directory), but
> also "Changed but not updated" and "Untracked files".  You cannot generate
> the latter two lists without checking with your work tree.

It seems like it shouldn't scan/show things outside of the path. If I've specified a path on the command line, I most likely only care about things in that path. I think it would make committing specific paths much faster when you have a large tree. However, it would eliminate information (changed/untracked files outside that path), if people are relying on that.

Previous: Boyd Stephen Smith Jr.Next: Boyd Stephen Smith Jr.
Message 4 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.