All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Johnson <palehose@gmail.com>
To: git@vger.kernel.org
Subject: Worktree "gitdir" file being mangled after upgrade to 2.7.0
Date: Wed, 13 Jan 2016 17:47:53 -0600	[thread overview]
Message-ID: <20160113234753.GA26473@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

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.

--

-Erik

"For me, it is far better to grasp the universe as it really is than to
persist in delusion, however satisfying and reassuring."  --Carl Sagan


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2016-01-13 23:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 23:47 Erik Johnson [this message]
2016-01-14  2:36 ` Worktree "gitdir" file being mangled after upgrade to 2.7.0 Junio C Hamano
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=20160113234753.GA26473@gmail.com \
    --to=palehose@gmail.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.
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.