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

Re: [RFC PATCH] status: avoid reporting worktrees as "Untracked files"

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 4, 2023, 06:58 UTC
Message-ID
<xmqqjzqygg3i.fsf@gitster.g>
In-Reply-To
<20231104000209.916189-1-eantoranz@gmail.com>
Edmundo Carmona Antoranz <eantoranz@gmail.com> writes:
> Given that worktrees are tracked in their own special fashion separately,
> it makes sense to _not_ report them as "untracked".

My gut feeling is that a much better solution to the unstated problem you are solving is to make sure that "git worktree add" will complain and not allow adding a subdirectory of any existing working tree of a repository as a new worktree.

What problem are you trying to solve? "git add foo" where "foo" is actually a different worktree of the repository would add it as a submodule that causes confusion? If that is the case, I think the right solution is not to get into such a state, i.e. not create a worktree of the repository inside a different worktree in the first place.

Previous: Eric SunshineNext: Edmundo Carmona Antoranz
Message 3 of 6 in “status: avoid reporting worktrees as "Untracked files"”
  1. status: avoid reporting worktrees as "Untracked files"Edmundo Carmona Antoranz, Nov 4, 2023
  2. Eric SunshineNov 4, 2023
  3. Junio C HamanoNov 4, 2023
  4. Edmundo Carmona AntoranzNov 11, 2023
  5. Eric SunshineNov 12, 2023
  6. Junio C HamanoNov 12, 2023

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.