From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 29 Jun 2012 20:23:54 GMT
Subject: Re: git submodule vs GIT_WORK_TREE
Message-ID: <7v4npt50kl.fsf@alter.siamese.dyndns.org>
In-Reply-To: <7v8vf551iu.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

>>> Declaring that a checked out submodule _must_ have its controlling
>>> repository as ".git" at its root level, i.e. it should be accessible
>>> without using GIT_WORK_TREE/GIT_DIR at all just like a normal Git
>>> repository is, would be a clean way to avoid the issue altogether
>>> and it still will allow the top-level superproject to be structured
>>> in a funny way to require GIT_WORK_TREE/GIT_DIR to access it,
>>
>> I fear this would make vcsh unable to support submodules, ever.
>
> Then think of a workable alternative.  As it stands, I would have to
> say that what vcsh tries to do with git is broken with respect to
> submodules.

Just to avoid misunderstanding.  I didn't mean "vcsh and vcsh alone
is broken while other solutions work just fine".  What I meant was
"I agree with you that what vcsh tries to do is unworkable".