# HG changeset patch
# User Arne Babenhauserheide <bab@draketo.de>
# Date 1242119364 -7200
# Node ID 83970c19b4952a19988471ffa7deb755c98b4ead
# Parent  60678b7a5eb06f9095de5046e0e618acf182754e
switched ssh repo url to user@example.com/path/ro/repo

diff -r 60678b7a5eb0 -r 83970c19b495 hgscm/templates/workflow_guide.html
--- a/hgscm/templates/workflow_guide.html	Tue May 12 10:51:09 2009 +0200
+++ b/hgscm/templates/workflow_guide.html	Tue May 12 11:09:24 2009 +0200
@@ -370,7 +370,7 @@
 
 <p>Note: To make this workflow more scaleable, each one of you can have his own BitBucket repository and you can simply <hg>pull</hg> from the others repositories. That way you can easily establish workflows in which certain people act as integrators and finally <hg>push</hg> checked code to a shared pull repository from which all others pull.</p>
 
-<p>Note: You can also use this workflow with a shared server instead of BitBucket, either via SSH or via a shared directory. An example for an SSH URL with Mercurial is be ssh://hg@bitbucket.org/ArneBab/hello (for a shared server you'd replace the "hg" in the given URL with your username). When using a shared directory you just push as if the repository in the shared directory were on your local drive.</p>
+<p>Note: You can also use this workflow with a shared server instead of BitBucket, either via SSH or via a shared directory. An example for an SSH URL with Mercurial is be ssh://user@example.com/path/to/repo. When using a shared directory you just push as if the repository in the shared directory were on your local drive.</p>
 
 <h3>Summary</h3>