From: Clement Moyroud <clement.moyroud@gmail.com>
To: git@vger.kernel.org
Subject: 'git rev-parse --show-toplevel' errors out with per-worktree configs
Date: Tue, 14 Jul 2020 12:40:40 -0700 [thread overview]
Message-ID: <CABXAcUxw5EA6jPB93C-Cfg-tycLMQSKUgrLkLXSQUZPHeEva9Q@mail.gmail.com> (raw)
Hello,
I have a bare repository clone that I create worktrees off. This works
fine, including 'git rev-parse --show-toplevel'.
I enabled per-worktree configs using 'git config --local
extensions.worktreeconfig=true', and now I can't get the toplevel
anymore:
> git rev-parse --show-toplevel
fatal: this operation must be run in a work tree
Disabling per-worktree configs makes it work again. This also works
fine on a non-bare repository clone.
IOW, this works:
git clone <url> non-bare
(cd non-bare && git worktree add -b master2 ../wtree1 master)
(cd wtree1 && git rev-parse --show-toplevel)
This does not:
git clone -c extensions.worktreeConfig=true <url> bare.git
(cd bare.git && git worktree add -b master2 ../wtree2 master)
(cd wtree2 && git rev-parse --show-toplevel)
Is this a bug, or am I missing something?
Thanks,
Clément
next reply other threads:[~2020-07-14 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 19:40 Clement Moyroud [this message]
2020-07-14 20:38 ` 'git rev-parse --show-toplevel' errors out with per-worktree configs Clement Moyroud
2020-07-14 21:34 ` Clement Moyroud
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=CABXAcUxw5EA6jPB93C-Cfg-tycLMQSKUgrLkLXSQUZPHeEva9Q@mail.gmail.com \
--to=clement.moyroud@gmail.com \
--cc=git@vger.kernel.org \
/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).