diff help/a-33.html @ 499:b3309be1640f

More help. This I think will do for 1.0.

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/help/a-33.html	Mon Aug 22 21:31:55 2011 +0100
@@ -0,0 +1,38 @@
+<link rel="stylesheet" type="text/css" href="help.css"/>
+
+
+<h2>I tried to push my changes, but it told me &ldquo;the remote repository may have been changed by someone else&rdquo; and refused</h2>
+
+<p>This error indicates that the remote repository has some changes in it
+that you do not have in your local repository (and that are in
+branches that you have also changed).  Perhaps someone else made these
+changes and pushed them, or they may have come from you pushing from a
+different computer.</p>
+
+<p>A good principle is that you should review and test your changes
+before you push them to another repository.  Although (with a
+distributed version control system) it's generally OK to commit
+changes locally that don't really work or that aren't complete enough
+to test, it's a bad idea to push anything that would cause the remote
+repository to have an untested set of changes in it.</p>
+
+<p>For that reason, if you change some files and someone else changes
+others and you both push them without knowing about the other one,
+Mercurial must refuse whichever push happens later &ndash; it won't simply
+merge the changes because the result might not make any sense.</p>
+
+<p>Instead you must pull the other person's changes and merge them
+locally before you push.  Fortunately, this is easy to do.</p>
+
+<p><b>1. Click Pull on the main toolbar at the top of the EasyMercurial window.</b>
+<ul><li>You should see that some changes are pulled and added to your local repository.  This will usually lead to a forked graph in the History pane, as your changes and the other user's were both started from the same parent at the same time.</li></ul></p>
+
+<p><b>2. Click Merge in the toolbar on the left.</b>
+<ul><li>Any changes that affect different files, or that affect different parts of the same file, will be merged automatically.  For changes that affect the same parts of the same file, you will be asked to choose which change to include in the merged copy.</li></ul></p>
+
+<p><b>3. Review or test the resulting merged version in your local working folder.</b></p>
+
+<p><b>4. Commit the merged version.</b></p>
+
+<p><b>5. Push again to the remote repository.</b></p>
+