From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Tue, 16 Apr 2013 08:21:34 GMT
Subject: Re: [RFC/PATCH] clone: introduce clone.submoduleGitDir to relocate $GITDIR
Message-ID: <CALkWK0=2+RY0cRSJD4pbHxPuqffDEqiwc7m0+Fzk7d8=wLvULQ@mail.gmail.com>
In-Reply-To: <7va9ozsk60.fsf@alter.siamese.dyndns.org>

Junio C Hamano wrote:
> It does not relieve "git add" (or "git submodulea add") from the
> responsibility of moving .git directory.  It only reduces the need
> to do so.
>
> When the user says "add" and the repository has .git directory in
> it, "add" (or "submodule add") is still responsible for relocating
> it.

Since you're so stubborn about it, I suppose 'git add' could call a
function in my "new first-class program to attach detach
worktrees/workdirs and relocate GITDIRs" as a last resort (if the user
somehow managed to put a GITDIR in the submodule worktree despite our
well-designed tools).  But last resort is not what we should be
discussing now: we're discussing what the design should ideally be.
And ideally, I think we both agree that it's best if init/clone did
the relocation.