EngineeringProductivity/HowTo/MirrorRepo: Difference between revisions

EngineeringProductivity/HowTo/MirrorRepo (view source)

2 bytes removed , 12 September 2012

m

947

edits

@@ Line 10: / Line 10: @@
 # Write your patch for [https://wiki.mozilla.org/Auto-tools/Projects/MozBase mozbase], attach it to your bug, get it reviewed, check it in to master and resolve the bug fixed [https://wiki.mozilla.org/Auto-tools/Projects/MozBase#Working_on_MozBase_and_contributing_patches per the mozbase procedure]. Now it is time to mirror the latest master to m-c.
 # Create a new bug called "Mirror mozbase to m-c for xyz" or similar and add your other bug as a dependency to make it clear why mirroring to m-c is desired.
-# Copy the entire (up-to-date) mozbase folder from [https://github.com/mozilla/mozbase] to the [https://github.com/mozilla/mozbase testing/mozbase] directory in m-c. Do not include .git, .gitignore, or versionbump.py
+# Copy the entire (up-to-date) mozbase folder from https://github.com/mozilla/mozbase to the [https://github.com/mozilla/mozbase testing/mozbase] directory in m-c. Do not include .git, .gitignore, or versionbump.py
 # Go to https://github.com/mozilla/mozbase/compare/mozilla-central...HEAD and examine the commits listed there. These are all the commits in master that aren't yet in m-c (i.e this is what you are committing to m-c). Pay special attention for commits that add or remove files and make sure to 'hg add' or 'hg rm' those exact same files in your m-c repository.
 # Generate a diff of m-c after you have copied the new mozbase there will files appropriately added and removed. Attach this to the bug.