X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ian/git?p=topgit.git;a=blobdiff_plain;f=README;h=66a1638c96890eed7e6c73810bde64cc3277b135;hp=89899041088cf0b3303d168eb9178b1fb9133ee3;hb=123b751dd8ef214efce19f0d453e608b74f873da;hpb=5996feaf0ff31de1350906aec3b60ed646be6bca

diff --git a/README b/README
index 8989904..66a1638 100644
--- a/README
+++ b/README
@@ -250,10 +250,26 @@ tg patch
 	TODO: tg patch -i to base at index instead of branch,
 		-w for working tree
 
+tg remote
+~~~~~~~~~
+	Register given remote as TopGit-controlled. This will create
+	the namespace for the remote branch bases and teach 'git fetch'
+	and 'git push' to operate on them.
+
+	It takes a mandatory remote name argument, and optional
+	'--populate' switch - use that for your origin-style remote,
+	it will seed the local topic branch system based on the
+	remote topic branches. '--populate' will also make 'tg remote'
+	automatically fetch the remote and 'tg update' to look at
+	branches of this remote for updates by default.
+
 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).
@@ -336,13 +352,25 @@ 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 tp/.
+
+	Usage: tg import rev1..rev2
+
 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.
@@ -434,7 +462,8 @@ self-contained topic system in the remote repository, and increased conceptual
 simplicity.
 
 Thus, we choose to instantiate all the topic branches of given remote locally;
-tg update will also check if a branch can be updated from its corresponding
+this is performed by 'tg remote --populate'.
+'tg update' will also check if a branch can be updated from its corresponding
 remote branch. The logic is somewhat involved if we should DTRT.
 First, we update the base, handling the remote branch as if it was the first
 dependency; thus, conflict resolutions made in the remote branch will be
@@ -442,3 +471,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.