Re: [PATCH 0/3] clone: respect configured fetch respecs during initial fetch

Jeff King writes: > On Wed, Nov 14, 2018 at 11:46:17AM +0100, SZEDER Gábor wrote: > >> This patch series should have been marked as v6, but I chose to reset >> the counter, because: >> >> - v5 was sent out way over a year ago [1], and surely everybody has >> forgotten about it since then

Re: [PATCH 0/3] clone: respect configured fetch respecs during initial fetch

On Wed, Nov 14, 2018 at 11:46:17AM +0100, SZEDER Gábor wrote: > This patch series should have been marked as v6, but I chose to reset > the counter, because: > > - v5 was sent out way over a year ago [1], and surely everybody has > forgotten about it since then anyway. But more

[PATCH 0/3] clone: respect configured fetch respecs during initial fetch

The initial fetch during a clone doesn't transfer refs matching additional fetch refspecs given on the command line as configuration variables, e.g. '-c remote.origin.fetch='. This contradicts the documentation stating that configuration variables specified via 'git clone -c = ...' "take effect