On 2012-11-27 14:19 , Justin Lebar wrote: >> - git.mozilla.org/releases/gecko.git only has the released branches for >> use by our partners (no other branches), but with CVS history > Would you mind explaining why we don't intend to add these additional > branches to git.mozilla.org? Better yet, I'll bring you into the next discussion on that process!
For this wide audience, I just wanted to clarify what is there, and not there, today. --Hal > From my perspective, the main lesson leaned from the past few months > is that maintaining multiple repositories is confusing for git users. > It seems to me that the clear winner is the approach in > github/mozilla/mozilla-central, where all branches are in the one > repository. > > On Tue, Nov 27, 2012 at 5:09 PM, Hal Wine <[email protected]> wrote: >> To clarify the repo situation a bit: >> >> - git.mozilla.org/releases/gecko.git only has the released branches for >> use by our partners (no other branches), but with CVS history >> >> - github.com/mozilla/mozilla-central has many more branches, and will >> be replaced in the near future with one where the sha's match >> git.mozilla.org >> >> There are quite a few FF developers who use the github repo - we will be >> working to minimize the pain for developers in moving repos (in large >> part based on Justin's nice writeups from the last emergency cutover). >> There will be lots of communication up front on that. >> >> >> >> On 2012-11-27 13:59 , Justin Lebar wrote: >>> In case you were curious, it turns out that: >>> >>> * The hashes in git.mozilla.org are different from the hashes in both >>> releases-mozilla-central and mozilla-central. >>> >>> * git.mozilla.org has full CVS history. >>> >>> John, do you know if there are plans to shut down >>> releases-mozilla-central? The fewer repositories we have sitting >>> around, the better. >>> >>> -Justin >>> >>> On Tue, Nov 27, 2012 at 4:09 PM, John Ford <[email protected]> wrote: >>>> Hi Team, >>>> >>>> We now have a Mozilla hosted Git server and tomorrow we will be pointing >>>> the master branch Gaia and Gecko at it tomorrow. I will be making this >>>> change tomorrow in the afternoon and will reply to this thread once the >>>> change is live. We've been using the Gecko repository from >>>> git.mozilla.org for the nightly builds for a week now, so they do work. >>>> The work to switch to git.mozilla.org is being tracked in bug 813710. >>>> >>>> Attached is the emulator and otoro manifests that will be live tomorrow in >>>> case you'd like to test this before it goes live. >>>> >>>> Please note that this repository has a different set of commit hashes than >>>> other repositories we've used for gecko. It would be prudent to make >>>> backups of your local copy of gecko before syncing to the manifests >>>> tomorrow. >>>> >>>> If you have any questions or if there are any critical concerns, please >>>> let me know as soon as possible. >>>> >>>> John >>>> >>>> >>>> >>>> _______________________________________________ >>>> dev-b2g mailing list >>>> [email protected] >>>> https://lists.mozilla.org/listinfo/dev-b2g >>>> _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
