X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ian/git?a=blobdiff_plain;ds=sidebyside;f=README;h=9c6f3352185130cf58f6158ffa96fd5ebbc1960d;hb=e5a36c029728f105f2376cad93bcb57153333081;hp=0c0002c7dd416c51bc22f05cc46cfca0306b1a75;hpb=4bf0ffdaa7d7f4ae21d50e72feb7372571971e10;p=topgit.git

diff --git a/README b/README
index 0c0002c..9c6f335 100644
--- a/README
+++ b/README
@@ -266,7 +266,10 @@ tg remote
 tg summary
 ~~~~~~~~~~
 	Show overview of all TopGit-tracked topic branches and their
-	up-to-date status ('0' marks that it introduces no own changes,
+	up-to-date status ('>' marks the current topic branch,
+	'0' marks that it introduces no own changes,
+	'l'/'r' marks that it is local-only or has remote mate,
+	'L'/'R' marks that it is ahead/out-of-date wrt. its remote mate,
 	'D' marks that it is out-of-date wrt. its dependencies,
 	'!' marks that it has missing dependencies (even recursively),
 	'B' marks that it is out-of-date wrt. its base).
@@ -349,13 +352,24 @@ tg export
 	TODO: For quilt exporting, use a temporary branch and remove it when
 	      done - this would allow producing conflict-less series
 
+tg import
+~~~~~~~~~
+	Import commits within the given revision range into TopGit,
+	creating one topic branch per commit, the dependencies forming
+	a linear sequence starting on your current branch.
+
+	The branch names are auto-guessed from the commit messages
+	and prefixed by t/ by default; use '-p PREFIX' to specify
+	an alternative prefix (even an empty one).
+
 tg update
 ~~~~~~~~~
 	Update the current topic branch wrt. changes in the branches
-	it depends on. This is made in two phases - first,
+	it depends on and remote branches.
+	This is performed in two phases - first,
 	changes within the dependencies are merged to the base,
-	then the base is merged into the topic branch. The output
-	will guide you in case of conflicts.
+	then the base is merged into the topic branch.
+	The output will guide you in case of conflicts.
 
 	In case your dependencies are not up-to-date, tg update
 	will first recurse into them and update these.
@@ -456,3 +470,8 @@ carried over to our local base automagically. Then, the base is merged into
 remote branch and the result is merged to local branch - again, to carry over
 remote conflict resolutions. In the future, this order might be adjustable
 per-update in case local changes are diverging more than the remote ones.
+
+All commands by default refer to the remote that 'tg remote --populate'
+was called on the last time ('topgit.remote' configuration variable). You can
+manually run any command with a different base remote by passing '-r REMOTE'
+_before_ the subcommand name.