git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Austin Morton <austin.morton@aquatic.com>
Cc: git@vger.kernel.org
Subject: Re: Able to checkout same branch in multiple worktrees when using symbolic-refs
Date: Fri, 29 Apr 2022 13:19:08 -0700	[thread overview]
Message-ID: <xmqqsfpvabib.fsf@gitster.g> (raw)
In-Reply-To: <CAAir=1MbwGtONW7yWRWoXKzAiwqwhOAqdhfWYMYLxt1vANuUOA@mail.gmail.com> (Austin Morton's message of "Fri, 29 Apr 2022 19:05:56 +0000")

Austin Morton <austin.morton@aquatic.com> writes:

> When using a symbolic-ref I am able to inadvertently checkout the same
> branch in multiple worktrees when using the symbolic-ref name, despite
> being prevented from doing so if I use the target branch name.

Don't do that if it hurts ;-)

If you checked out 'main' in the secondary worktree and made a
commit there, the symbolic-ref makes 'master' to be updated,
confusing the primary worktree whose index and the working tree
files record work relative to the old commit before the secondary
worktree updated it via the symbolic-ref, which is exactly the same
situation that the "do not check out the same branch in two
different worktrees" protection tries to save the user from, but I
do not think we currently do so.

Because this "do not check a branch out twice and let it be futzed
with from the two places" is primarily a mechanism to help
inexperienced users from getting confused (and there is an escape
hatch mechanism to allow it to those who know what they are doing),
and use of symbolic-ref to make 'main' and 'master' synonyms with
each other is not something inexperienced users who have no clue on
what they are doing would be doing anyway, it may not be a huge
deal.

I also suspect there is no way, other than scanning _all_ the local
branches, to see if some other branch aliases the branch we are
about to check out.  It may potentially be somewhat expensive.

But it would be nice if it can get fixed in inexpensively.

Thanks for a report.


> Below is a minimal reproducer:
>
> $ git --version
> git version 2.36.0
> $ git init .
> $ git status
> $ git commit --allow-empty -m "Initial commit"
> $ git symbolic-ref refs/heads/main refs/heads/master
> $ git worktree add ../worktree2
> $ git worktree list
> /home/amorton/test/worktree1 cd8312d [master]
> /home/amorton/test/worktree2 cd8312d [worktree2]
> $ cd ../worktree2
> $ git checkout master
> fatal: 'master' is already checked out at '/home/amorton/test/worktree1'
> $ git checkout main
> Switched to branch 'main'
> $ git worktree list
> /home/amorton/test/worktree1 cd8312d [master]
> /home/amorton/test/worktree2 cd8312d [master]

  reply	other threads:[~2022-04-29 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 19:05 Able to checkout same branch in multiple worktrees when using symbolic-refs Austin Morton
2022-04-29 20:19 ` Junio C Hamano [this message]
2022-05-02 14:54   ` Austin Morton
2022-05-02 18:30     ` Junio C Hamano

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=xmqqsfpvabib.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=austin.morton@aquatic.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.
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).