Not updating crosses branches bagong dating
Whatever you do, don't do 'push -f' like the message suggests.
(It'll probably fail anyway, but don't try it.) Someone pushed new commits upstream since your last pull.
which includes 8 lines of context and shows the relevant function for the block.
You can make these options default in the Mercurial configuration file.
You also have to tell ssh what username to use when connecting to hg.
These are a good idea to use all the time when you're learning mercurial. (It could be trivial or it could be a huge headache.
And even once you're an expert, always doing outgoing before push is a good idea. Sometimes the tree will be under sheriff control, and they will specifically ask for a bundle. There's plenty about merging elsewhere in this FAQ.) Your push of many changesets was bad, but you didn't find out until after a lot of subsequent activity.
If you don't have sufficient rights to push to mozilla-central, you might also generate bundles and attach them to bugs when you add checkin-needed to a bug after it has the necessary reviews and approval. Once you have your changes all done, commit them to your local repository. Once you have everything committed, instead of pushing you'll run Your backout changeset is based on an old revision. You want to back out the bad but keep the probably-good changesets from the subsequent activity.
Please refer to Mercurial For Mozillians at Read The Docs for current best-practices around Mercurial, including many helpful extra tools and guidelines that make using Mercurial fast and easy.
This document describes techniques and practices like mercurial queues which are no longer recommended.
The interactive setup wizard can guide you through the process of configuring Mercurial to submit commits to Mozilla: part if you're not sure who is going to review your bug; the person who does the final check-in of the patch will make sure it's added.