On Tue, Feb 04, 2014 at 11:20:39AM +0100, Daniel Hahler wrote: > Hi, > > when using a submodule "sm", there is a relative worktree in its config: > > .git/modules/sm/config: > [core] > worktree = ../../../smworktree > > git-new-worktree (from contrib) symlinks this config the new worktree. > > From inside the new worktree, git reads the config, but resolves the > relative worktree setting based on the symlink's location. Hmm.. core.worktree is relative to $GIT_DIR. Whether "config" is a symlink should have no effects. $ pwd /tmp/abc $ ls -l .git/config lrwxrwxrwx 1 pclouds users 11 Feb 9 15:57 .git/config -> /tmp/config $ cat /tmp/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true worktree = ../../worktree $ ls -l /tmp/worktree/ total 4 -rw-r--r-- 1 pclouds users 5 Feb 9 15:59 abc $ ~/w/git/git ls-files -o abc Maybe it's something else. Could you produce a small test case? > A fix would be to resolve any relative worktree setting based on the > symlink target's location (the actual config file), and not from the > symlink. > > This is with git version 1.8.5.3. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html