Note, for git lovers, the git remote hg helper seems to work quite well. see http://felipec.wordpress.com/2012/11/13/git-remote-hg-bzr-2/
As an occasional gecko developer I'm giving it a try right now and see how it goes :) Le 26/11/2013 20:13, Juan Gómez a écrit : > Well, I have a fork of mozilla/mozilla-central and it is not disabled. I > can push commits, browse it via web or clone it. > Anyway, What do you suggest? moving to git.mozilla.org instead of > github/gecko-dev? > > > > On Tue, Nov 26, 2013 at 2:05 AM, Gregory Szorc <g...@mozilla.com> wrote: > >> It looks like GitHub decided to disable Ehsan's repo and all forks without >> notice. https://bugzilla.mozilla.org/show_bug.cgi?id=943132 tracks it >> from our end. >> >> >> On 11/25/13, 11:39 PM, Ehsan Akhgari wrote: >> >>> Dear all, >>> >>> For the past two and a half years I have been maintaining a git mirror >>> of mozilla-central plus a lot of the other branches that people found >>> useful at https://github.com/mozilla/mozilla-central. Over the years >>> this proved to be too much work for me to keep up with, and given the >>> existence of the new git mirrors that are supported by RelEng, I'm >>> planning to shut down the update jobs for this repository on Friday, Dec >>> 13, 2013 and take the repository down. >>> >>> I strongly suggest that if you have been using and relying on this >>> repository before, please consider switching to the RelEng repositories >>> as soon as possible. https://github.com/mozilla/gecko-dev is the main >>> repository where you can find branches such as trunk/aurora/b2g >>> branches/etc and https://github.com/mozilla/gecko-projects is a >>> repository which contains project branches and twigs. (Note that my >>> repository hosts all of these branches in a single location, but from >>> now on if you use both of these branch subsets you will need to have two >>> upstream remotes added in your local git clone.) >>> >>> The RelEng repositories have a similar history line including the CVS >>> history but they have completely different commit SHA1s, so pulling that >>> repo into your existing clones is probably not what you want. If you >>> don't have a lot of non-merged branches, your safest bet is cloning from >>> scratch and then port your existing branches manually. If you have a >>> lot of local branches, you may want to wait for the script that John >>> Schoenick is working on in bug 929338 which will assist you in rebasing >>> those branches on top of the new history line. >>> >>> Last but not least, I really hate to have to disrupt your workflow like >>> this. I do hope that three weeks is enough advance notice for everybody >>> to successfully switch over to the new mirrors, but if you have a reason >>> for me to delay this please let me know and I will do my best to >>> accommodate. >>> >>> Cheers, >>> -- >>> Ehsan >>> <http://ehsanakhgari.org/> >>> >>> >>> _______________________________________________ >>> firefox-dev mailing list >>> firefox-...@mozilla.org >>> https://mail.mozilla.org/listinfo/firefox-dev >>> >>> >> _______________________________________________ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform >> > _______________________________________________ > dev-b2g mailing list > dev-...@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
