Junio C Hamano <[email protected]> writes:
> Jeff King <[email protected]> writes:
>
>>> And in my current understanding of submodules the check in
>>> .gitmodules ought to be enough, too.
>>
>> Yeah, that probably makes sense. You can have a gitlink without a
>> .gitmodules file, but I don't quite know what that would mean in terms
>> of submodules (I guess it's not a submodule but "something else").
>
> That may be a lot better than reading the index unconditionally, but
> I'd rather not to see "git rev-parse" read ".gitmodules" at all. It
> would discourage scripted use of Git for no good reason.
Thinking about this more, I suspect that
cd sub && git anything
when the index of the top-level thinks "sub" must be a submodule and
the user is not interested in "sub" (hence it hasn't gone through
"git submodule init" or "update") should get the same error as you
would get if you did
cd /var/tmp/ && git anything
when none of /, /var, /var/tmp/ is controlled by any Git repository.
I.e. "fatal: Not a git repository".
Perhaps we can update two things and make it cheap.
- checking out the top-level working tree without populating the
working tree of a submodule learns to do a bit more than just
creating an empty directory. Instead, it creates the third kind
of ".git" (we currently support two kinds of ".git", one that is
a repository itself, and another that is points at a repository),
that tells us that there is not (yet) a repository there.
- the "discovering the root of the working tree" logic learns to
notice the third kind of ".git" and stop with "Not a git
repository".
