From: Eric Sunshine <sunshine@sunshineco.com>
To: Lobachevksiy Vitaliy <numzer0@yandex.ru>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Worktrees attached to bare repo don't work
Date: Sun, 13 Sep 2020 00:49:59 -0400 [thread overview]
Message-ID: <CAPig+cRqkzPzNX8UN4OcgEOOKbtZRLCjNNiZsOVkGBy0pvsEkQ@mail.gmail.com> (raw)
In-Reply-To: <3b57a5b2-a34e-de95-38c7-9bc6923a8eba@yandex.ru>
On Sat, Sep 12, 2020 at 4:01 PM Lobachevksiy Vitaliy <numzer0@yandex.ru> wrote:
> I have a bare repository and several worktrees attached to it. That was
> working fine until recent update. Now when I try virtually any git
> command like `git status` in any attached worktree, or even in a new
> one, it prints `fatal: this operation must be run in a work tree`.
> The workaround is simply `git config --worktree --add core.bare false`
> in each worktree.
This is happening because you have apparently set the configuration
variable extensions.worktreeConfig to true. As far as I can tell by
reading the "Configuration File" section of the "git worktree"
documentation and by consulting the commit[1] which introduced
extensions.worktreeConfig, this is working as intended. According to
the "git worktree" documentation, configuration core.bare is no longer
specially filtered out when inside a worktree once
extensions.worktreeConfig is enabled, so you need to move the
core.bare=true setting out of the bare.git/config and into
bare.git/config.worktree to prevent the worktrees from seeing that
setting. Once that's done, you don't need the per-worktree
core.bare=false setting you've been using as a workaround.
[1]: https://lore.kernel.org/git/20181021140228.24941-3-pclouds@gmail.com/
prev parent reply other threads:[~2020-09-13 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 19:59 Worktrees attached to bare repo don't work Lobachevksiy Vitaliy
2020-09-13 4:49 ` Eric Sunshine [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cRqkzPzNX8UN4OcgEOOKbtZRLCjNNiZsOVkGBy0pvsEkQ@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=numzer0@yandex.ru \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).