Re: Need to set GIT_WORK_TREE when setting GIT_DIR !?

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Mar 10, 2012, 14:05 UTC
Message-ID: <CACsJy8AUo3+ECdxfnyfYGA-mAtHB8KBOUrie3_Qo3cyfshZmAA@mail.gmail.com>
In-Reply-To: <4F5B55E8.4080000@gmail.com>

2012/3/10 Frédéric Heitzmann <frederic.heitzmann@gmail.com>:

Show 17 quoted lines

> However man git-config says :
>
> "If --git-dir or GIT_DIR is specified but none of --work-tree, GIT_WORK_TREE
> and core.worktree is specified, the
> current working directory is regarded as the top level of your working
> tree."
>
> Some more context on my precise problem :
> I have a project, with source files managed with git.
> I also use some Makefiles that I would like to manage with git _in a
> separate repository_
>
> $ GIT_DIR=<project_path>/.git git add some_file.c ...
> $ GIT_DIR=<project_path>/.git_mk git add Makefile ...
>
> Setting worktree in each GIT_DIR/config will fix that but I can't figure out
> why current git implementation actually needs this.

Historical reason: before separate worktree feature was introduced, git assumed worktree was at $GIT_DIR's parent directory. Old scripts may rely on that behavior.

-- 
Duy