diff --git a/README.md b/README.md index 4a480133b29a2bffd91dd6af4497f78bac036f30_UkVBRE1FLm1k..dfed3bd84184a9c05a6b414ed7541dc722c6c496_UkVBRE1FLm1k 100644 --- a/README.md +++ b/README.md @@ -22,6 +22,11 @@ hg clone git://github.com/schacon/hg-git.git +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 explicit protocol prefix (mind the switch from colon to slash after the host!): + + git clone git@github.com:schacon/hg-git.git + 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: cd hg-git # (an Hg repository) @@ -25,8 +30,8 @@ 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: cd hg-git # (an Hg repository) - (edit .hg/hgrc and add the target git url in the path section) + (edit .hg/hgrc and add the target git url in the paths section) hg push This will convert all your Hg data into Git objects and push them up to the Git server. @@ -29,14 +34,7 @@ hg push This will convert all your Hg data into Git objects and push them up to the Git server. -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 explicit protocol prefix (mind the -switch from colon to slash after the host!): - - git clone git@github.com:schacon/hg-git.git - hg clone git+ssh://git@github.com/schacon/hg-git.git - Now that you have an Hg repository that can push/pull to/from a Git repository, you can fetch updates with `hg pull`. $ hg pull @@ -46,7 +44,7 @@ Hg Bookmarks Integration ======================== -Hg-Git works will use your bookmarks if you have any or have the bookmarks extension enabled. It will allow you to push your bookmarks up to the Git server as branches and will pull Git branches down and set them up as bookmarks if you want. +If you have the bookmarks extension enabled, Hg-Git will use it. It will push your bookmarks up to the Git server as branches and will pull Git branches down and set them up as bookmarks. This is actually pretty cool, since you can use this extension to transfer your Hg bookmarks via the Git protocol, rather than having to scp them, as the Hg transfer protocol does not currently support transferring bookmarks.