Jeff King writes:
> IMHO, we should stick to the conceptual model that "git clone" is:
>
> git init
> git config ... ;# set up remote, etc
> git fetch
> git checkout ;# obviously not for --bare
>
> The implementation has to diverge from that to do certain optimizations,
> but absent any g
On Mon, Mar 07, 2016 at 04:19:31PM +0100, SZEDER Gábor wrote:
> >Even though I think the original description did not mean to include
> >the fetch refspecs when it talked about configuration taking effect,
> >I think what this change wants to do probably makes sense.
>
> Well, currently one would
Quoting Junio C Hamano :
SZEDER Gábor writes:
Check whether there are any relevant configured fetch refspecs and
take those into account during the initial fetch, unless running 'git
clone --single-branch'.
Signed-off-by: SZEDER Gábor
---
Even though I think the original description did
SZEDER Gábor writes:
> Check whether there are any relevant configured fetch refspecs and
> take those into account during the initial fetch, unless running 'git
> clone --single-branch'.
>
> Signed-off-by: SZEDER Gábor
> ---
Even though I think the original description did not mean to include
Configuration variables specified via 'git clone -c ='
"take effect immediately after the repository is initialized, but
before the remote history is fetched". This implies that any fetch
refspecs specified this way should already be taken into account
during the initial fetch and remote refs matc
5 matches
Mail list logo
