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

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Nov 12, 2023, 17:13 UTC
Message-ID: <CAPig+cQbwcJOQiYyb7bma3pH1hxjE_X_yeAp3JeHWVCeJtySfQ@mail.gmail.com>
In-Reply-To: <CAOc6etbowajhHsctFJN4ZQ0gND0jzZUrhEkep_pLYtE9y9RBCQ@mail.gmail.com>

On Sat, Nov 11, 2023 at 4:22 AM Edmundo Carmona Antoranz <eantoranz@gmail.com> wrote:

Show 14 quoted lines

> On Sat, Nov 4, 2023 at 7:58 AM Junio C Hamano <gitster@pobox.com> wrote:
> > 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.
> >
> Hey, guys! Thanks Junio and Eric for sharing your thoughts.
>
> I am not against the idea of creating worktrees outside of the
> repository... however, I like them to be _inside_ the repository. Am I
> the only one? IDK. I might be! It feels completely natural, if you ask
> me.... but that's just my opinion, I acknowledge that.

I doubt you're the only one, but, based upon, list emails over the years, it seems that both in-main-tree and outside-main-tree (often sibling) worktrees are common. More recently, we've also heard from people who don't even have a main-worktree; instead, they hang their multiple worktrees off of a bare repository (which is an explicitly-supported use-case); i.e.:

    git clone --bare https://.../foobar.git
    git -C foobar.git worktree add worktree1
    git -C foobar.git worktree add worktree2
    ...