[webkit-dev] Changing Github repository to mirror git.webkit.org (was Github vs. git.webkit.org)

Jesus Sanchez-Palencia jesus at webkit.org
Wed Jan 16 04:55:16 PST 2013


Hi,

The mirror is finally ready again: https://github.com/WebKit/webkit
It now follows the same hashes of git.webkit.org. People who have
forked this repository on github before will now have to rebase their
branches.

I was hold back a bit because Github wasn't allowing me to push more
than 2GB. I contacted them but before I could get answer I decide to
'split' the push. First I git reset --hard the repository back to a
commit from 2008, pushed this, then reset --hard to 2009 and pushed
this, and so on.

In the middle of the process the folks from github increased our push
limit to 20GB and David (barrbrain) was kind enough to push one last
sync, getting us back to 2012. After that I kept the syncing manullay
for a few hours but now the repository is being updated automatically
every 5 minutes to stay in sync with git.webkit.org .

I will now coordinate with William so we can get Apple pushing to the
mirror at the same time they push to git.webkit.org .

Thanks everyone that got involved for the help!

Cheers,
jesus

2013/1/14 Jesus Sanchez-Palencia <jesus at webkit.org>:
> Hi,
>
> Just yet another quick heads-up:
>
>> 2013/1/14 Jesus Sanchez-Palencia <jesus at webkit.org>:
>>> We have decided that the best approach for this is to start a new
>>> repository (webkit-mirror), delete the old one
>>> (https://github.com/WebKit/webkit) and then rename the new repository.
>
> I had to change my strategy here after talking to a few people on #github.
> It seems that doing a "git push -f" to the current repository
> (https://github.com/WebKit/webkit) will actually have less impact on
> people branching/forking it on github. In other words, it should be
> less painful to rebase your fork on github for the new hashes after
> I'm done with the setup.
>
> I will let you know when the switching is done.
>
> Cheers,
> jesus
>
>>>
>>> I will be doing the mirroring myself for while, until Apple can set
>>> this up from the same machine that git pushes to git.webkit.org.
>>>
>>> People that are using the current github repository will probably have
>>> to re-clone and rebase their branches.
>>>
>>> This won't affect git.webkit.org or any other official WebKit repository.
>>>
>>>
>>> Cheers,
>>> jesus
>>>
>>>
>>>
>>> 2012/12/11 Jesus Sanchez-Palencia <jesus.palencia at openbossa.org>:
>>>> Hi,
>>>>
>>>> 2012/12/4 Tor Arne Vestbø <tor.arne.vestbo at digia.com>:
>>>>>
>>>>> Bill, what do you think about pushing the official SVN import to GitHub as
>>>>> well?
>>>>>
>>>>> tor arne
>>>>
>>>> Any updates about this?
>>>>
>>>> Cheers,
>>>> jesus
>>>>
>>>>
>>>>>
>>>>>>
>>>>>> So we might be able to rename the existing one and ask github to pull
>>>>>> our git.webkit.org <http://git.webkit.org> repository into
>>>>>>
>>>>>> github/WebKit/webkit.
>>>>>> Apparently Apache takes that way: https://github.com/apache
>>>>>> The "mirroring" icon indicates kind of official-ness.
>>>>>>
>>>>>> I don't know how long their mirroring delay is, though.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Dec 1, 2012 at 12:07 AM, Tor Arne Vestbø
>>>>>> <tor.arne.vestbo at digia.com <mailto:tor.arne.vestbo at digia.com>> wrote:
>>>>>>
>>>>>>     On 11/28/12 16:55 , Adam Barth wrote:
>>>>>>
>>>>>>         My sense is that the WebKit community would prefer that the
>>>>>>         hashes in
>>>>>>         GitHub match the hashes in git.webkit.org
>>>>>>         <http://git.webkit.org> so that folks can more
>>>>>>
>>>>>>         easily move branches between the two.  For my part, I've
>>>>>>         switched over
>>>>>>         to using GitHub exclusive of git.webkit.org
>>>>>>         <http://git.webkit.org>, so the the difference in
>>>>>>
>>>>>>         hashes aren't an issue for me, but I can understand why they'd be
>>>>>>         problematic for other people.
>>>>>>
>>>>>>
>>>>>>     Yepp, agreed. Let's switch it over.
>>>>>>
>>>>>>
>>>>>>         After the force-push, would you still be able to push updates
>>>>>>         automatically?  If so, you can switch the hashes whenever is
>>>>>>         convenient for you.  (It might be nice to announce the date/time
>>>>>> on
>>>>>>         this list so that folks aren't taken by surprise.)
>>>>>>
>>>>>>
>>>>>>     The mirror is also pushed to http://gitorious.org/webkit/__webkit
>>>>>>     <http://gitorious.org/webkit/webkit>, which I was planning to keep
>>>>>>
>>>>>>     as is for now, so that would mean setting up an extra mirroring for
>>>>>>     the non-author-rewritten history :/ Also, the server I run this on
>>>>>>     has a somewhat uncertain future. With that in mind it's probably
>>>>>>     easier to just push directly from the same import that's pushed to
>>>>>>     git.webkit.org <http://git.webkit.org>, and make the GitHub mirror
>>>>>>
>>>>>>     an official mirror?
>>>>>>
>>>>>>     tor arne
>>>>>>
>>>>>>     _________________________________________________
>>>>>>     webkit-dev mailing list
>>>>>>     webkit-dev at lists.webkit.org <mailto:webkit-dev at lists.webkit.org>
>>>>>>     http://lists.webkit.org/__mailman/listinfo/webkit-dev
>>>>>>     <http://lists.webkit.org/mailman/listinfo/webkit-dev>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> webkit-dev mailing list
>>>>>> webkit-dev at lists.webkit.org
>>>>>> http://lists.webkit.org/mailman/listinfo/webkit-dev
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> webkit-dev mailing list
>>>>> webkit-dev at lists.webkit.org
>>>>> http://lists.webkit.org/mailman/listinfo/webkit-dev


More information about the webkit-dev mailing list