Re: Bug? git worktree fails with master on bare repo

From: Duy Nguyen <pclouds@gmail.com>
Date: Oct 10, 2016, 09:45 UTC
Message-ID: <CACsJy8DMKWeZ+DuQ0uoY6rdPfusq8D1SfBCkPyn+6X9S589ncg@mail.gmail.com>
In-Reply-To: <CAOi_75+Zoeeq5FD1HKgG4MjeL9LkBshsSfdrMOTi8m-Mt-OQNQ@mail.gmail.com>

On Sun, Oct 9, 2016 at 8:42 PM, Michael Tutty <mtutty@gforgegroup.com> wrote:

Show 7 quoted lines

> Dennis,
> Thanks for the great response, and for spending time on my issue.
> I'll try that first patch and see what happens.
>
> In the meantime, it got weirder...
>
> I created a brand-new (bare) repo

Elaboration needed here. If I create a bare _clone_, then "HEAD" could be detached, or point to some branch, depending on where "HEAD" is in the source repo. If source repo's HEAD is "master", I got the same behavior (worktree add fails). If it's detached or points to some other branch, it's ok. If this is "git init --bare" then I got "fatal: invalid reference: master".

Show 5 quoted lines

> and was able to git add worktree
> /path master.  I was able to do this repeatedly, even using the
> worktree to merge other branches to master.  I didn't find any
> condition or step that caused some kind of orphan master work tree,
> which was what I thought the underlying problem might be.

-- 
Duy