Skip to content
Snippets Groups Projects
Commit 37ff4189 authored by Tay Ray Chuan's avatar Tay Ray Chuan
Browse files

README: make url conversion more explicit

Previously, we just threw two clone commands (one for git and one for
hg) at the reader.
parent 3f0ceaf3
No related branches found
No related tags found
No related merge requests found
......@@ -26,5 +26,10 @@
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
......@@ -30,5 +35,10 @@
$ 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:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment