X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ian/git?a=blobdiff_plain;f=README;h=a4839f45803b62ec2dcf06eda571c4b51fa89bf7;hb=897a2bd3fdb31a1372ac3f522befa2d5a5f7c07a;hp=dc2e5ff320bbf788e2d5aed02602a0753990584b;hpb=ab712f2ed92a6e451bf2d482b03d2559697bf100;p=topgit.git

diff --git a/README b/README
index dc2e5ff..a4839f4 100644
--- a/README
+++ b/README
@@ -203,7 +203,10 @@ tg create
 	the current branch is assumed to be the only dependency.
 
 	After `tg create`, you should insert the patch description
-	to the '.topmsg' file.
+	to the '.topmsg' file, which will already contain some
+	pre-filled bits. You can set topgit.to, topgit.cc and topgit.bcc
+	configuration variables in order to have `tg create`
+	add these headers with given default values to '.topmsg'.
 
 	The main task of `tg create` is to set up the topic branch
 	base from the dependencies. This may fail due to merge conflicts.
@@ -242,7 +245,7 @@ tg patch
 
 	The patch is by default simply dumped to stdout. In the future,
 	tg patch will be able to automatically send the patches by mail
-	or save them to files.
+	or save them to files. (TODO)
 
 	TODO: tg patch -i to base at index instead of branch,
 		-w for working tree
@@ -306,6 +309,8 @@ mail headers are inserted and the patch itself is appended.
 Thus, as your patches evolve, you can record nuances like whether
 the paricular patch should have To-list/Cc-maintainer or vice
 versa and similar nuances, if your project is into that.
+From is prefilled from your current GIT_AUTHOR_IDENT, other headers
+can be prefilled from various optional topgit.* config options.
 
 	.topdeps: Contains the one-per-line list of branches
 your patch depends on, pre-seeded with `tg create`. (Continuously