On 07/02/2014 07:10 PM, Alex Vandiver wrote:
> On 07/02/2014 06:20 PM, Junio C Hamano wrote:
>> Alex Vandiver writes:
>>
>>> [remote "github"]
>>> url = g...@github.com:bestpractical/rt.git
>>> fetch = +refs/*:refs/*
>>> mirror = yes
>>
>> "git push github master^:maste
On 07/02/2014 06:20 PM, Junio C Hamano wrote:
> Alex Vandiver writes:
>
>> [remote "github"]
>> url = g...@github.com:bestpractical/rt.git
>> fetch = +refs/*:refs/*
>> mirror = yes
>
> "git push github master^:master" must stay a usable way to update
> the published r
Alex Vandiver writes:
> [remote "github"]
> url = g...@github.com:bestpractical/rt.git
> fetch = +refs/*:refs/*
> mirror = yes
"git push github master^:master" must stay a usable way to update
the published repository to an arbitrary commit, so "if set to
mirror, do n
Heya,
We recently ran into a particularly troubling race condition, discovered
in git 2.0.0. The setup for it is as follows:
The repository is a bare repository, which developers push to via ssh;
it mirrors its changes out onto github. In its config:
[remote "github"]
url = g...@gi
4 matches
Mail list logo