I just ran into the same issue and ended up here. While the comments above lead to the correct answer, they may not cut it for a person new to Mercurial who wants to contribute to an open source project.
A plain hg pull
would only pull any changes from your fork to your local cloned repository, not helpful in this case. There is an optional parameter [SOURCE]
that allows you to pull from the trunk instead.
Here are the Mercurial command-line commands needed to do the job (replace "someprojectname" accordingly for your desired CodePlex project or, for similar systems, replace the entire URL with your fork's trunk's URL [vs. your fork's URL]):
- [Optional] See what changesets are in trunk but not in your local repository:
hg incoming https://hg01.codeplex.com/someprojectname
- Pull new changesets to your repository:
hg pull https://hg01.codeplex.com/someprojectname
- Merge those changes into your own code (resolving conflicts accordingly):
hg merge
- Commit the results to your local repository:
hg commit -m "Some message about merging changes from trunk."
- Push the updated version of your code from your local repository to your fork on CodePlex:
hg push
merge
command? – Caldronhg pull
, and then you dohg merge
to merge the two heads. – Caldron