Re: [RFC] On the --depth argument when fetching with submodules

2016-02-08 Thread Jonathan Nieder
Hi, Stefan Beller wrote: > 1) You work on the superproject and don't care about the submodules. > In this case you want the superproject non-shallow and the submodules > may be just fine with depth 1. (Think of libraries pulled in via Git instead > of via the build system) > > 2) The superproject

Re: [RFC] On the --depth argument when fetching with submodules

2016-02-08 Thread Junio C Hamano
Stefan Beller writes: > ... Instead of the branch, you can just pass > a sha1 to git fetch and it sometimes works (if the server permits fetching > arbitrary or hidden sha1s. Though Jonathan noted this check may be in > the client only and the server trusts the client on not wanting arbitrary > s

Re: [RFC] On the --depth argument when fetching with submodules

2016-02-08 Thread Stefan Beller
On Sun, Feb 7, 2016 at 5:32 AM, Lars Schneider wrote: > > On 06 Feb 2016, at 01:05, Junio C Hamano wrote: > >> Stefan Beller writes: >> >>> Currently when cloning a project, including submodules, the --depth argument >>> is passed on recursively, i.e. when cloning with "--depth 2", both the >>>

Re: [RFC] On the --depth argument when fetching with submodules

2016-02-07 Thread Lars Schneider
On 06 Feb 2016, at 01:05, Junio C Hamano wrote: > Stefan Beller writes: > >> Currently when cloning a project, including submodules, the --depth argument >> is passed on recursively, i.e. when cloning with "--depth 2", both the >> superproject as well as the submodule will have a depth of 2.

Re: [RFC] On the --depth argument when fetching with submodules

2016-02-05 Thread Fredrik Gustafsson
On Fri, Feb 05, 2016 at 04:05:01PM -0800, Junio C Hamano wrote: > Stefan Beller writes: > > > Currently when cloning a project, including submodules, the --depth argument > > is passed on recursively, i.e. when cloning with "--depth 2", both the > > superproject as well as the submodule will have

Re: [RFC] On the --depth argument when fetching with submodules

2016-02-05 Thread Junio C Hamano
Stefan Beller writes: > Currently when cloning a project, including submodules, the --depth argument > is passed on recursively, i.e. when cloning with "--depth 2", both the > superproject as well as the submodule will have a depth of 2. It is not > garantueed that the commits as specified by th

[RFC] On the --depth argument when fetching with submodules

2016-02-05 Thread Stefan Beller
Currently when cloning a project, including submodules, the --depth argument is passed on recursively, i.e. when cloning with "--depth 2", both the superproject as well as the submodule will have a depth of 2. It is not garantueed that the commits as specified by the superproject are included in t