Confirmed users
4,971
edits
ReleaseEngineering/How To/VCSSync: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/VCSSync (view source)
Revision as of 22:11, 14 October 2013
, 14 October 2013→How to deal with completely resetting gecko-projects
| Line 56: | Line 56: | ||
# Edit the README with the contents you downloaded in step 4. | # Edit the README with the contents you downloaded in step 4. | ||
# Start the conversion back up. You may only need to delete the build/target and build/stage_source/BAD_REPO directories. Or you may need to blow away the whole thing from orbit to be sure, in which case you should follow the docs for [https://wiki.mozilla.org/ReleaseEngineering/VCSSync/HowTo#How_to_start_a_mozilla-central_based_repo_conversion_from_scratch how to start a mozilla-central based repo conversion from scratch]. | # Start the conversion back up. You may only need to delete the build/target and build/stage_source/BAD_REPO directories. Or you may need to blow away the whole thing from orbit to be sure, in which case you should follow the docs for [https://wiki.mozilla.org/ReleaseEngineering/VCSSync/HowTo#How_to_start_a_mozilla-central_based_repo_conversion_from_scratch how to start a mozilla-central based repo conversion from scratch]. | ||
#* Note, just cloning the hg repos for the projects repo can take many many hours, so this will take the gecko-projects repo down for a long time. | |||
=== How to deal with GECKO90_2011121217_RELBRANCH === | === How to deal with GECKO90_2011121217_RELBRANCH === | ||