From: Junio C Hamano <gitster@pobox.com>
To: worley@alum.mit.edu (Dale R. Worley)
Cc: git@vger.kernel.org
Subject: Re: [git-users] Problem using detached worktrees with commands implemented in scripts
Date: Fri, 18 Oct 2013 15:43:52 -0700 [thread overview]
Message-ID: <xmqqy55qurmf.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <201310182225.r9IMP4i3002659@freeze.ariadne.com> (Dale R. Worley's message of "Fri, 18 Oct 2013 18:25:04 -0400")
worley@alum.mit.edu (Dale R. Worley) writes:
>> From: Junio C Hamano <gitster@pobox.com>
>
>> Side note: without GIT_WORK_TREE environment (or
>> core.worktree), there is no way to tell where the top level
>> is, so you were limited to always be at the top level of
>> your working tree if you used GIT_DIR to refer to a
>> repository that is not embedded in your working tree. There
>> were some changes in this area, but I do not recall the
>> details offhand.
>
> That's not true. The core.worktree config variable tells the top of
> the worktree, so once you've located the repository, you know where
> the worktree is.
Read the second line again, perhaps?
> ... it's not clear why GIT_WORK_TREE exists, ...
The configuration item came _way_ later than the environment, and we
need to keep users and scripts from old world working, that is why.
next prev parent reply other threads:[~2013-10-18 22:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 20:03 [git-users] Problem using detached worktrees with commands implemented in scripts Dale R. Worley
2013-10-16 21:42 ` Junio C Hamano
2013-10-16 22:39 ` Philip Oakley
2013-10-16 23:08 ` Junio C Hamano
2013-10-17 20:11 ` Philip Oakley
2013-10-17 20:50 ` Junio C Hamano
2013-10-17 21:14 ` Philip Oakley
2013-10-17 22:38 ` Philip Oakley
2013-10-17 22:48 ` Jonathan Nieder
2013-10-18 20:40 ` Philip Oakley
2013-10-18 22:54 ` Dale R. Worley
2013-10-17 19:09 ` Dale R. Worley
2013-10-17 20:08 ` Junio C Hamano
2013-10-18 22:25 ` Dale R. Worley
2013-10-18 22:43 ` Junio C Hamano [this message]
2013-10-21 18:51 ` Dale R. Worley
2013-10-18 22:50 ` Dale R. Worley
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy55qurmf.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=worley@alum.mit.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).