Changes

<div id="legacy"></div><b>See [http://people.mozilla.org/~hwine/tmp/vcs2vcs/ legacy docs] for the legacy (aka "old") process.</b>

 === How to add a repo to gecko-dev or gecko-git ==='''''CAUTION:''' production gecko.git is still handled by legacy vcs-sync - make changes theresee [http://people.mozilla.org/~hwine/tmp/vcs2vcs/cookbook.html#adding-a-branch-to-gecko-git legacy docs].''<br />This shouldn't be done lightly. Gecko.git is our partner-oriented repo and should be treated with kid gloves. === How to add another repo to mirror for b2g OS ===Mirroring repositories for purpose of b2g os builds is handled by the legacy docs. See [http://people.mozilla.org/~hwine/tmp/vcs2vcs/cookbook.html#mirroring-a-git-repository here].=== How to add a repo to gecko-dev ===gecko-dev is our developer focused repository with all gecko branches related to release-trains and inbound-branches only.