Re: [RFC/PATCH] clone: introduce clone.submoduleGitDir to relocate $GITDIR
- From
Marc Branchaud <marcnarc@xiplink.com>
- Date
- Apr 15, 2013, 18:50 UTC
- Message-ID
- <516C4BEB.7030507@xiplink.com>
- In-Reply-To
- <CALkWK0n0y6OPJvYjNeEbUx_CC58vHRRLCsmJtws+RKyv3wRTwQ@mail.gmail.com>
On 13-04-15 02:00 PM, Ramkumar Ramachandra wrote:
Show 9 quoted lines
> Junio C Hamano wrote: >> >> I do not think the addition Ram is envisioning in the patch will >> prevent you from teaching "add" to do that. An implemention of such >> an addition indeed would most likely use the same --separate-git-dir >> mechanism anyway. > > Well, I'm against the change in principle because add operates on > worktree paths, not URLs. I don't want to change that arbitrarily.
I don't understand that statement.
If "git add" is all about specifying what lives under paths in the worktree, what's wrong with letting "git add" go beyond specifying just files?
Syntax aside for the moment, I think a command like git add git-repo-reference foo is perfectly natural: It specifies what is inside worktree path foo.
M.