On Wed, May 25, 2016 at 3:38 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> Sometimes the history of a submodule is not considered important by
>> the projects upstream. To make it easier for downstream users, allow
>> a field 'submodule..depth' in .gitmodules, which can be used
>> to ind
Stefan Beller writes:
> Sometimes the history of a submodule is not considered important by
> the projects upstream. To make it easier for downstream users, allow
> a field 'submodule..depth' in .gitmodules, which can be used
> to indicate the recommended depth.
Hmph. I can understand and certa
Sometimes the history of a submodule is not considered important by
the projects upstream. To make it easier for downstream users, allow
a field 'submodule..depth' in .gitmodules, which can be used
to indicate the recommended depth.
Stefan Beller (3):
submodule update: make use of the existing f
3 matches
Mail list logo