comparison help/topics/32.txt @ 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 {Sharing changes} 1 {Sharing changes}
2 2
3 I want to push my changes to a master repository shared with my colleagues 3 I want to put my changes into a master repository shared with my colleagues
4 4
5 Setting up such a repository with a properly configured remote server
6 is out of the scope of this Help, but you generally want one of the
7 following:
8
9 *A server that everyone on your team has secure ssh access to*, _or_
10
11 *An account with a managed online Mercurial hosting service*
12
13 With either of the above, you should be able to create a new
14 repository on the server and obtain a Mercurial URL for it. That may
15 be a _ssh://host/path_ URL in the former case, or the URL (often an
16 _https_ one) provided by the service in the latter case.
17
18 In EasyMercurial, you then:
19
20 *1. Go to Remote -> Set Remote Location.., enter the URL of the remote repository and click OK.*
21
22 * This tells EasyMercurial to use that URL as the default location for subsequent push and pull operations.
23
24 *2. Click Push on the main toolbar at the top of the EasyMercurial window.*
25
26 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.
31
32 For this to work, the target repository must be _related_ 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.
37