Pasha Bolokhov <pasha.bolok...@gmail.com> writes:
> 1) an apparent missing "normalize_path(git_dir)", when GIT_DIR is an
> absolute path:
> don't even need to name the repository anything different, but run this
> $ cd ~/tmp/
> $ git init
> $ git --git-dir=$HOME/tmp/../tmp/./././.git --work-tree=$HOME/tmp/../tmp/
> You won't notice anything different in the output of course, but the
> environment will be odd:
> Notice how the work-tree has been normalized and git-dir hasn't. It's
> kinda hard to imagine when this can lead to an error, but never know.
I think this one is in the "if it hurts, don't do it then"
> Would there be objections to fixing this?
As long as it can be cleanly done without penalizing sane usage, I
do not think there will be.
> 2) "git --git-dir=meta status" complains:
> $ git --git-dir=meta init
> $ git --git-dir=meta status
> yells that work-tree isn't setup and denies to run.
Is that because meta/config does not say where the worktree is?
Again, this smells like "if it hurts, don't do it then", even more
so than the previous one. Does it help if you add --git-work-tree
to the command line, too?
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