[PATCH 2/2] submodule update: learn `--[no-]recommend-shallow` option

2016-05-26 Thread Stefan Beller
Sometimes the history of a submodule is not considered important by the projects upstream. To make it easier for downstream users, allow a boolean field 'submodule..shallow' in .gitmodules, which can be used to recommend whether upstream considers the history important. This field is honored in th

Re: [PATCH 2/2] submodule update: learn `--[no-]recommend-shallow` option

2016-05-26 Thread Stefan Beller
On Thu, May 26, 2016 at 2:07 AM, Remi Galan Alfonso wrote: > You forgot to update from recommend-depth to recommend-shallow > > Stefan Beller writes: >> [...] >> 'git submodule' [--quiet] init [--] [...] >> 'git submodule' [--quiet] deinit [-f|--force] (--all|[--] ...) >> 'git submodule' [--qu

Re: [PATCH 2/2] submodule update: learn `--[no-]recommend-shallow` option

2016-05-26 Thread Remi Galan Alfonso
You forgot to update from recommend-depth to recommend-shallow Stefan Beller writes: > [...] > 'git submodule' [--quiet] init [--] [...] > 'git submodule' [--quiet] deinit [-f|--force] (--all|[--] ...) > 'git submodule' [--quiet] update [--init] [--remote] [-N|--no-fetch] > - [-f|

[PATCH 2/2] submodule update: learn `--[no-]recommend-shallow` option

2016-05-25 Thread Stefan Beller
Sometimes the history of a submodule is not considered important by the projects upstream. To make it easier for downstream users, allow a boolean field 'submodule..shallow' in .gitmodules, which can be used to recommend whether upstream considers the history important. This field is honored in th