Chris@498: Chris@498: Chris@498: Chris@499:

I want to put my changes into a master repository shared with my colleagues

Chris@498: Chris@499:

Setting up such a repository with a properly configured remote server Chris@499: is out of the scope of this Help, but you generally want one of the Chris@499: following:

Chris@499: Chris@499:

A server that everyone on your team has secure ssh access to, or

Chris@499: Chris@499:

An account with a managed online Mercurial hosting service

Chris@499: Chris@499:

With either of the above, you should be able to create a new Chris@499: repository on the server and obtain a Mercurial URL for it. That may Chris@499: be a ssh://host/path URL in the former case, or the URL (often an Chris@499: https one) provided by the service in the latter case.

Chris@499: Chris@499:

In EasyMercurial, you then:

Chris@499: Chris@499:

1. Go to Remote -> Set Remote Location.., enter the URL of the remote repository and click OK. Chris@499:

This tells EasyMercurial to use that URL as the default location for subsequent push and pull operations.

Chris@499: Chris@499:

2. Click Push on the main toolbar at the top of the EasyMercurial window.

Chris@499: Chris@499:

This will push all of the changes that you have made in your local Chris@499: repository (since you pushed to the same target, if you ever have). Chris@499: You should do this regularly whenever you have a coherent set of Chris@499: changes for others to use or test. Your colleagues can then pull from Chris@499: the same remote repository URL to obtain your changes.

Chris@499: Chris@499:

For this to work, the target repository must be related to the local Chris@499: one. That means either a repository that has been pulled to, or Chris@499: pushed to from, the local repository before; or the repository that Chris@499: was initially used to clone the local one from; or else an empty Chris@499: repository.

Chris@499: