# HG changeset patch
# User Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
# Date 1546033178 -3600
# Node ID 634c2fa427e8b1ab3eb7bda7edbe83d7a4c33540
# Parent  14e8dcffd279274429473ec1880dca06bc86b822
docs: upgrade: make upgrade instructions from version control more explicit

Instruct users to make a note of the orginal and new revision, both to help
in any failure analysis, and also to let them realize when the 'hg update'
command failed.

diff -r 14e8dcffd279 -r 634c2fa427e8 docs/upgrade.rst
--- a/docs/upgrade.rst	Fri Dec 28 22:38:02 2018 +0100
+++ b/docs/upgrade.rst	Fri Dec 28 22:39:38 2018 +0100
@@ -81,10 +81,14 @@
 
     pip install --upgrade kallithea
 
-If you originally installed from version control, it is as simple as::
+If you originally installed from version control, assuming you did not make
+private changes (in which case you should adapt the instructions accordingly)::
 
     cd my-kallithea-clone
-    hg pull -u
+    hg parent   # make a note of the original revision
+    hg pull
+    hg update
+    hg parent   # make a note of the new revision
     pip install --upgrade -e .
     kallithea-cli front-end-build