Just as I was looking for our revision to answer TB3b1 opting-in, I've
seen that we have multiple heads in our hg repo, due to tagging for
Firefox 3.1 build and release. Should I hg merge, or ignore it?
(Learning the Mercurial way is going to take some time, sorry; please,
be patient with us). :-)
Ricardo
You should *not* merge. This new head belongs to a named Mercurial branch.
You should keep using the `default` branch.
--BDS
Usually, just
hg pull
hg update
will do that. Unless you happened to get off the default branch, then
just make sure to be on the default branch by
hg update -r default
Axel