From: John Szakmeister <john@szakmeister.net>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Bug with worktrees...
Date: Fri, 28 Aug 2015 06:27:46 -0400 [thread overview]
Message-ID: <CAEBDL5W9Ly_tsE35OG+MGZkA0V41FEoewZTWk9EPZxXQHnRF6A@mail.gmail.com> (raw)
In-Reply-To: <CAPig+cTkeOywRH1-_4Zi9jOd5r1cXa9vJhYAYXhF3E+SSE_GeA@mail.gmail.com>
On Thu, Aug 27, 2015 at 10:55 PM, Eric Sunshine <sunshine@sunshineco.com> wrote:
[snip]
> I can reproduce with 2.5.0 but not 'master'. Bisection reveals that
> this was fixed by d95138e (setup: set env $GIT_WORK_TREE when work
> tree is set, like $GIT_DIR, 2015-06-26), and was reported previously
> here [1].
I had done a quick search but didn't turn up that thread. Thank you Eric!
-John
prev parent reply other threads:[~2015-08-28 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 19:03 Bug with worktrees John Szakmeister
2015-08-28 2:55 ` Eric Sunshine
2015-08-28 10:27 ` John Szakmeister [this message]
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=CAEBDL5W9Ly_tsE35OG+MGZkA0V41FEoewZTWk9EPZxXQHnRF6A@mail.gmail.com \
--to=john@szakmeister.net \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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 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 NNTP newsgroup(s).