Quoting Junio C Hamano :
SZEDER Gábor writes:
Quoting Junio C Hamano :
IOW, special casing -c remote.origin.fetch=spec
is a bad idea.
I completely agree :)
But it's the other way around.
'remote.origin.fetch=spec' during clone is special _now_, because the
initial fetch ignores it, no m
Quoting Junio C Hamano :
SZEDER Gábor writes:
Conceptually 'git clone' should behave as if the following commands
were run:
git init
git config ... # set default configuration and origin remote
git fetch
git checkout # unless '--bare' is given
However, that initial 'git fetch' be
SZEDER Gábor writes:
> Quoting Junio C Hamano :
>
>> IOW, special casing -c remote.origin.fetch=spec
>> is a bad idea.
>
> I completely agree :)
> But it's the other way around.
>
> 'remote.origin.fetch=spec' during clone is special _now_, because the
> initial fetch ignores it, no matter where i
Quoting Junio C Hamano :
IOW, special casing -c remote.origin.fetch=spec
is a bad idea.
I completely agree :)
But it's the other way around.
'remote.origin.fetch=spec' during clone is special _now_, because the
initial fetch ignores it, no matter where it is set.
My patch makes it non-speci
Junio C Hamano writes:
> Is the expectation like this?
>
> git init
> git config ... # set default configuration and origin remote
> git config var val # update with what "-c var=val" told us
> git fetch
> git checkout # unless '--bare' is given
>
> or is it something else?
SZEDER Gábor writes:
> Conceptually 'git clone' should behave as if the following commands
> were run:
>
> git init
> git config ... # set default configuration and origin remote
> git fetch
> git checkout # unless '--bare' is given
>
> However, that initial 'git fetch' behaves differen
Conceptually 'git clone' should behave as if the following commands
were run:
git init
git config ... # set default configuration and origin remote
git fetch
git checkout # unless '--bare' is given
However, that initial 'git fetch' behaves differently from any
subsequent fetches, becaus
7 matches
Mail list logo
