From: "Gabriel Nützi" <gnuetzi@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: GIT_DIR output from git worktree list
Date: Wed, 30 Sep 2020 09:34:42 +0200 [thread overview]
Message-ID: <335b6e6a-9527-5444-da80-08faf43db606@gmail.com> (raw)
In-Reply-To: <CAPig+cTwNwt+_f4FYDqy5xVsDVU3pqfKXtK6GKtWLLqbU6Y8Vg@mail.gmail.com>
Am 30.09.2020 um 07:33 schrieb Eric Sunshine:
> On Tue, Sep 29, 2020 at 1:31 PM Gabriel Nützi <gnuetzi@gmail.com> wrote:
>> When you do move the .git folder somewhere else:
>>
>> git init Test && cd Test && mv .git .git-b
>> git --git-dir=.git-b --work-tree . worktree list
>>
>> the output is :
>> ..../Test/.git-b 0000000 [master]
>>
>> Why is the output a .git Dir and not a worktree. I expected `.../Test`.
> Because the implementation doesn't really look for or know where the
> main worktree is. Instead, it's taking the path of the repository and
> stripping off "/.git" if present, and reporting that as the main
> worktree. Under normal circumstances this works just fine because
> either (a) the repository _is_ the .git directory within the main
> worktree, or (b) it's a bare repository and there is no main worktree,
> thus it reports the repository path instead of the non-existent main
> worktree.
Ok, it's kind of sad that as far as I understood, there is probably always only this heuristic about stripping ".git"
because the main worktree path is not registered inside the .git dir or somewhere else.
I mean you can technically name the git directory what ever you want and in that case how is that stripping than going to work?
But of course when you do so, you probably need to set either GIT_DIR, or or use --git-dir
Also what I realized is, isn't the doc a bit inexact about GIT_DIR:
> GIT_DIR is the location of the .git folder.
Shouldn't it read: GIT_DIR is the path of the .git folder. Location could mean its the parent folder? Hm...
> I suppose one way to fix this would be to specially check if
> --work-tree or GIT_WORK_TREE is specified and use that value as the
> path of the main worktree. (This special case would only be used when
> computing the main worktree path; it would not be used when computing
> linked worktree paths.)
Probably, --work-tree, GIT_WORK_TREE or core.worktree.
Thanks Eric!
BR
next prev parent reply other threads:[~2020-09-30 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 17:30 GIT_DIR output from git worktree list Gabriel Nützi
2020-09-30 5:33 ` Eric Sunshine
2020-09-30 7:34 ` Gabriel Nützi [this message]
2020-09-30 20:35 ` Eric Sunshine
2020-12-07 4:34 ` Eric Sunshine
2020-12-07 7:28 ` Ganriel Nützi
2020-12-08 19:27 ` Eric Sunshine
2020-12-09 9:30 ` Duy Nguyen
2020-12-13 6:07 ` Eric Sunshine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=335b6e6a-9527-5444-da80-08faf43db606@gmail.com \
--to=gnuetzi@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).