Annoying absolute path for "core.worktree" to submodule

[Christian Hammerl <info@christian-hammerl.de>]

Hey folks,

I really love the work you are doing on GIT but the last update
regarding submodules is a bit annoying. Although the path inside the
".git" file is stored relative to the submodule's path, the path in
".git/modules/path-to-submodule/config" is stored as an absolute path
for "core.worktree".

I develop (for some projects) within a chroot where I have a different
username and therefore the path differs if I am currently inside the
chroot or not. If the submodule is initialized inside the chroot, I
always get this message when I cd into the project's directory outside
of the chroot:

fatal: Could not switch to
'/home/chroot-username/parent-path-of-submodule': File or directory not
found
fatal: 'git status --porcelain' failed in submodule
relative-path-to-submodule

This is caused by using `__git_ps1` for my bash-prompt. I don't know
exactly where the problem is and what actions (called by __git_ps1) are
responsible for this.

Any suggestions how to deal with this?

And no, removing __git_ps1 from my bash-prompt is not the answer, I
like this feature very much. ;-)

Thanks in advance
Christian