# HG changeset patch
# User J. H. Palmieri <palmieri@math.washington.edu>
# Date 1278636162 25200
# Node ID 73ebae9a5f86a5eb69d98607a56b1d49c64e78bc
# Parent f5e6724a274008cd284bbcac19b98a555a3cc667
#9433: add command hg_root for new repository
diff git a/doc/en/developer/producing_patches.rst b/doc/en/developer/producing_patches.rst
a

b


134  134  
135  135   ``SAGE_ROOT/local/bin``: Sage shell scripts. 
136  136  
 137   ``SAGE_ROOT``: Sage root  text files in the main Sage directory 
 138  and in ``SAGE_ROOT/spkg``. 
 139  
137  140  The previous section discussed using Mercurial with the Sage library, 
138  141  via the command ``hg_sage``. There are corresponding commands for each 
139  142  of the repositories: 
… 
… 

144  147  
145  148   use ``hg_scripts`` for the Sage shell scripts. 
146  149  
 150   use ``hg_root`` for the Sage root. 
 151  
147  152  Since version 3.4, both the Sage library and documentation 
148  153  repositories are managed by the command ``hg_sage``. 
diff git a/sage/misc/all.py b/sage/misc/all.py
a

b


36  36  
37  37  from dist import install_scripts 
38  38  
39   from hg import hg_sage, hg_scripts, hg_extcode, hg_sagenb 
 39  from hg import hg_sage, hg_scripts, hg_extcode, hg_sagenb, hg_root 
40  40  
41  41  from package import install_package, is_package_installed, standard_packages, optional_packages, experimental_packages, upgrade 
42  42  
diff git a/sage/misc/hg.py b/sage/misc/hg.py
a

b


1265  1265  push_url='%s/examples/'%SAGE_OUTGOING_SERVER, 
1266  1266  obj_name='examples') 
1267  1267  
 1268  hg_root = HG(SAGE_ROOT, 
 1269  'Sage Root', 
 1270  pull_url=SAGE_INCOMING_SERVER, 
 1271  push_url=SAGE_OUTGOING_SERVER, 
 1272  obj_name='root') 
 1273  
1268  1274  hg_sagenb = HG('%s/devel/sagenb' % SAGE_ROOT, 
1269  1275  'SageNB Source Code', 
1270  1276  pull_url='http://boxen.math.washington.edu:8123', 