Mercurial > hg-website
changeset 159:83970c19b495
switched ssh repo url to user@example.com/path/ro/repo
| author | Arne Babenhauserheide <bab@draketo.de> |
|---|---|
| date | Tue, 12 May 2009 11:09:24 +0200 |
| parents | 60678b7a5eb0 |
| children | bb60a4d6a1e3 |
| files | hgscm/templates/workflow_guide.html |
| diffstat | 1 files changed, 1 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- 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>