Mercurial > hg > hg-git

changeset 330:37ff4189b05b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
README: make url conversion more explicit Previously, we just threw two clone commands (one for git and one for hg) at the reader.
author Tay Ray Chuan <rctay89@gmail.com>
date Mon, 17 May 2010 22:31:43 +0800
parents 3f0ceaf30344
children c3ecdfcb91e7
files README.md
diffstat 1 files changed, 12 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/README.md
+++ b/README.md
@@ -26,9 +26,19 @@
 hg-git would clone the repository down into the directory 'munger.git', then
 convert it to an Hg repository for you.
 
-If you want to clone a github repository for later pushing (or any other repository you access via ssh), you need to convert the ssh url to a format with an explicit protocol prefix (mind the switch from colon to slash after the host!):
+If you want to clone a github repository for later pushing (or any other repository you access via ssh), you need to convert the ssh url to a format with an explicit protocol prefix. For example, the git url with push
+access
+
+    git@github.com:schacon/hg-git.git
+
+would read
 
-    $ git clone git@github.com:schacon/hg-git.git
+    git+ssh://git@github.com/schacon/hg-git.git
+
+(Mind the switch from colon to slash after the host!)
+
+Your clone command would thus look like this:
+
     $ hg clone git+ssh://git@github.com/schacon/hg-git.git
 
 If you are starting from an existing Hg repository, you have to setup a Git repository somewhere that you have push access to, add it as default path or default-push path in your .hg/hgrc and then run `hg push` from within your project.  For example: