Explain when to use post-clone-retired

[code/vcsh.git] / README.md

diff --git a/README.md b/README.md
index 68031ff877ef0dd23dfb7733e0efbdedd350b421..a83325d979ee4482a828111802d7882a4dbe141c 100644 (file)
--- a/README.md
+++ b/README.md
@@ -56,8 +56,9 @@ Let's say you want to version control your `vim` configuration:
     vcsh vim commit -m 'Initial commit of my Vim configuration'
     # optionally push your files to a remote
     vcsh vim remote add origin <remote>
     vcsh vim commit -m 'Initial commit of my Vim configuration'
     # optionally push your files to a remote
     vcsh vim remote add origin <remote>

-    vcsh vim push origin master:master
-    vcsh vim branch --track master origin/master
+    vcsh vim push -u origin master
+    # from now on you can push additional commits like this
+    vcsh vim push

 
 If all that looks a _lot_ like standard `git`, that's no coincidence; it's
 a design feature.
 
 If all that looks a _lot_ like standard `git`, that's no coincidence; it's
 a design feature.


@@ -365,7 +366,7 @@ ignore this fact for now and follow the examples.
 
 ## Initialize a new repository "vim"
 
 
 ## Initialize a new repository "vim"
 

-    vcsh init vcsh
+    vcsh init vim

 
 ## Clone an existing repository
 
 
 ## Clone an existing repository