Re: [PATCH 0/6] git clone: Marry --recursive and --reference

2016-08-05 Thread Junio C Hamano
Stefan Beller writes: > The plan for other layouts might be > > git submodule update --reference-dir /var/cache/ That is not a plan for "other layouts", but a plan for "the other layout that was mentioned as a possibility". As I said, both layouts are equally plausible, and I do not know if

Re: [PATCH 0/6] git clone: Marry --recursive and --reference

2016-08-05 Thread Stefan Beller
On Fri, Aug 5, 2016 at 12:47 PM, Junio C Hamano wrote: > * You want the "clone" command above with "--recursive" to do "the >right thing". That is, the clone of the superproject borrows >from /var/cache/super.git local mirror, and the clone of xyzzy >that would be made at .git/module

Re: [PATCH 0/6] git clone: Marry --recursive and --reference

2016-08-05 Thread Junio C Hamano
Stefan Beller writes: > Currently when cloning a superproject with --recursive and --reference > only the superproject learns about its alternates. The submodules are > cloned independently, which may incur lots of network costs. > > Assume that the reference repository has the submodules a

[PATCH 0/6] git clone: Marry --recursive and --reference

2016-08-04 Thread Stefan Beller
Currently when cloning a superproject with --recursive and --reference only the superproject learns about its alternates. The submodules are cloned independently, which may incur lots of network costs. Assume that the reference repository has the submodules at the same paths as the to-be-clo