Re: Bug: relative core.worktree is resolved from symlink and not its target

2014-02-17 Thread Duy Nguyen
On Mon, Feb 17, 2014 at 4:36 PM, Daniel Hahler wrote: > On 09.02.2014 10:08, Duy Nguyen wrote: >> On Tue, Feb 04, 2014 at 11:20:39AM +0100, Daniel Hahler wrote: > > Thanks for looking into this. > >>> when using a submodule "sm", there is a relative worktree in its config: >>> >>>.git/modules/

Re: Bug: relative core.worktree is resolved from symlink and not its target

2014-02-17 Thread Daniel Hahler
On 09.02.2014 10:08, Duy Nguyen wrote: > On Tue, Feb 04, 2014 at 11:20:39AM +0100, Daniel Hahler wrote: Thanks for looking into this. >> when using a submodule "sm", there is a relative worktree in its config: >> >>.git/modules/sm/config: >>[core] >> worktree = ../../../smworktree >>

Re: Bug: relative core.worktree is resolved from symlink and not its target

2014-02-09 Thread Duy Nguyen
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 workt

Bug: relative core.worktree is resolved from symlink and not its target

2014-02-04 Thread Daniel Hahler
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 relati