From: Kevin Daudt <me@ikke.info>
To: Michael Tutty <mtutty@gforgegroup.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
Dennis Kaarsemaker <dennis@kaarsemaker.net>,
Git Mailing List <git@vger.kernel.org>,
Michael Rappazzo <rappazzo@gmail.com>
Subject: Re: Bug? git worktree fails with master on bare repo
Date: Tue, 11 Oct 2016 17:41:37 +0200 [thread overview]
Message-ID: <20161011154137.GA20160@ikke.info> (raw)
In-Reply-To: <CAOi_75KR+AEAD540L=GtQ7jH5ngTFdHMq53+FzjzAfsZtTqfwg@mail.gmail.com>
On Mon, Oct 10, 2016 at 08:06:47AM -0500, Michael Tutty wrote:
>
> > If source repo's HEAD is "master", I got the same behavior (worktree add fails)
>
> So if it's possible for a bare repo to have HEAD pointing at master,
> is there a safe way for me to change this (e.g., as a cleanup step
> before doing my actual merge process)?
You can change where HEAD points to in a bare repositor with `git
symbolic-ref HEAD <branch>`, but note that this changes what branch gets
checked out when cloning a repository.
Where users would normally check out master by default, after changing
what HEAD points to, it would be that branch (or detached when HEAD
doesn't even point at a branch).
next prev parent reply other threads:[~2016-10-11 15:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 0:30 Bug? git worktree fails with master on bare repo Michael Tutty
2016-10-09 6:50 ` Kevin Daudt
2016-10-09 7:51 ` Dennis Kaarsemaker
2016-10-09 10:52 ` Duy Nguyen
2016-10-09 13:42 ` Michael Tutty
2016-10-10 9:45 ` Duy Nguyen
2016-10-10 13:06 ` Michael Tutty
2016-10-11 15:41 ` Kevin Daudt [this message]
2016-10-12 16:41 ` [PATCH] worktree: allow the main brach of a bare repository to be checked out Dennis Kaarsemaker
2016-10-12 17:35 ` Michael Tutty
2016-10-12 18:37 ` Junio C Hamano
2016-10-12 18:50 ` Junio C Hamano
2016-10-13 10:31 ` Duy Nguyen
2016-10-12 19:23 ` Dennis Kaarsemaker
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=20161011154137.GA20160@ikke.info \
--to=me@ikke.info \
--cc=dennis@kaarsemaker.net \
--cc=git@vger.kernel.org \
--cc=mtutty@gforgegroup.com \
--cc=pclouds@gmail.com \
--cc=rappazzo@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.