> From: Junio C Hamano <gits...@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.

Indeed, it's not clear why GIT_WORK_TREE exists, as that allows the
user to set GIT_WORK_TREE inconsistently with core.worktree.  (What
happens if you do that?)

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to