public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail•com>,
	"Michael Rappazzo" <rappazzo@gmail•com>
Cc: git@vger•kernel.org, Erik Johnson <palehose@gmail•com>
Subject: Re: Worktree "gitdir" file being mangled after upgrade to 2.7.0
Date: Wed, 13 Jan 2016 18:36:16 -0800	[thread overview]
Message-ID: <xmqqh9iglwf3.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160113234753.GA26473@gmail.com> (Erik Johnson's message of "Wed, 13 Jan 2016 17:47:53 -0600")

Erik Johnson <palehose@gmail•com> writes:

> Since upgrading to 2.7.0 last week, eventually I'll get to a point when
> I run 'git worktree list' where several worktrees are incorrectly
> reported as pointing to my main git checkout. Further analysis of the
> files in $GIT_DIR/worktrees/worktree_name/ shows that the gitdir file
> for the worktrees which display incorrectly contains ".git" instead of
> what it should contain (i.e. "/path/to/worktree/.git".
>
> This was reported a couple days ago on Github:
>
> https://github.com/git/git-scm.com/issues/650
>
> Since the audiences for the mailing list and Github don't overlap
> completely, I figured I'd report it here to get this issue in front of
> as many eyes as possible.

Thanks for relaying.  Duy, Michael, I think this is your area?

  reply	other threads:[~2016-01-14  2:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 23:47 Worktree "gitdir" file being mangled after upgrade to 2.7.0 Erik Johnson
2016-01-14  2:36 ` Junio C Hamano [this message]
2016-01-14  3:29   ` Duy Nguyen
2016-01-14 13:58     ` Mike Rappazzo
2016-01-15 17:52       ` Junio C Hamano
2016-01-14 18:36 ` Andreas Schwab

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=xmqqh9iglwf3.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=palehose@gmail$(echo .)com \
    --cc=pclouds@gmail$(echo .)com \
    --cc=rappazzo@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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