Mercurial > hg > easyhg
comparison help/a-32.html @ 499:b3309be1640f
More help. This I think will do for 1.0.
| author | Chris Cannam |
|---|---|
| date | Mon, 22 Aug 2011 21:31:55 +0100 |
| parents | 21aa41b62c3a |
| children |
comparison
equal
deleted
inserted
replaced
| 498:21aa41b62c3a | 499:b3309be1640f |
|---|---|
| 1 <link rel="stylesheet" type="text/css" href="help.css"/> | 1 <link rel="stylesheet" type="text/css" href="help.css"/> |
| 2 | 2 |
| 3 | 3 |
| 4 <h2>I want to push my changes to a master repository shared with my colleagues</h2> | 4 <h2>I want to put my changes into a master repository shared with my colleagues</h2> |
| 5 | 5 |
| 6 <p>Setting up such a repository with a properly configured remote server | |
| 7 is out of the scope of this Help, but you generally want one of the | |
| 8 following:</p> | |
| 9 | |
| 10 <p><b>A server that everyone on your team has secure ssh access to</b>, <i>or</i></p> | |
| 11 | |
| 12 <p><b>An account with a managed online Mercurial hosting service</b></p> | |
| 13 | |
| 14 <p>With either of the above, you should be able to create a new | |
| 15 repository on the server and obtain a Mercurial URL for it. That may | |
| 16 be a <i>ssh://host/path</i> URL in the former case, or the URL (often an | |
| 17 <i>https</i> one) provided by the service in the latter case.</p> | |
| 18 | |
| 19 <p>In EasyMercurial, you then:</p> | |
| 20 | |
| 21 <p><b>1. Go to Remote -> Set Remote Location.., enter the URL of the remote repository and click OK.</b> | |
| 22 <ul><li>This tells EasyMercurial to use that URL as the default location for subsequent push and pull operations.</li></ul></p> | |
| 23 | |
| 24 <p><b>2. Click Push on the main toolbar at the top of the EasyMercurial window.</b></p> | |
| 25 | |
| 26 <p>This will push all of the changes that you have made in your local | |
| 27 repository (since you pushed to the same target, if you ever have). | |
| 28 You should do this regularly whenever you have a coherent set of | |
| 29 changes for others to use or test. Your colleagues can then pull from | |
| 30 the same remote repository URL to obtain your changes.</p> | |
| 31 | |
| 32 <p>For this to work, the target repository must be <i>related</i> to the local | |
| 33 one. That means either a repository that has been pulled to, or | |
| 34 pushed to from, the local repository before; or the repository that | |
| 35 was initially used to clone the local one from; or else an empty | |
| 36 repository.</p> | |
| 37 |
