The options available are:
+.TP
+\-\-cc
+Specify a starting "Cc:" value for each email\&.
+
.TP
\-\-chain\-reply\-to, \-\-no\-chain\-reply\-to
If this is set, each email will be sent as a reply to the previous email sent\&. If disabled with "\-\-no\-chain\-reply\-to", all emails after the first will be sent as replies to the first email sent\&. When using this, it is recommended that the first file given be an overview of the entire patch series\&. Default is \-\-chain\-reply\-to
\-\-in\-reply\-to
Specify the contents of the first In\-Reply\-To header\&. Subsequent emails will refer to the previous email instead of this if \-\-chain\-reply\-to is set (the default) Only necessary if \-\-compose is also set\&. If \-\-compose is not set, this will be prompted for\&.
+.TP
+\-\-no\-signed\-off\-by\-cc
+Do not add emails foudn in Signed\-off\-by: lines to the cc list\&.
+
.TP
\-\-quiet
Make git\-send\-email less verbose\&. One line per email should be all that is output\&.
\-\-subject
Specify the initial subject of the email thread\&. Only necessary if \-\-compose is also set\&. If \-\-compose is not set, this will be prompted for\&.
+.TP
+\-\-suppress\-from
+Do not add the From: address to the cc: list, if it shows up in a From: line\&.
+
.TP
\-\-to
Specify the primary recipient of the emails generated\&. Generally, this will be the upstream maintainer of the project involved\&.
.SH "SYNOPSIS"
-git\-svnimport [ \-o <branch\-for\-HEAD> ] [ \-h ] [ \-v ] [ \-d | \-D ] [ \-C <GIT_repository> ] [ \-i ] [ \-u ] [\-l limit_rev] [ \-b branch_subdir ] [ \-T trunk_subdir ] [ \-t tag_subdir ] [ \-s start_chg ] [ \-m ] [ \-M regex ] <SVN_repository_URL> [ <path> ]
+\fIgit\-svnimport\fR [ \-o <branch\-for\-HEAD> ] [ \-h ] [ \-v ] [ \-d | \-D ] [ \-C <GIT_repository> ] [ \-i ] [ \-u ] [\-l limit_rev] [ \-b branch_subdir ] [ \-T trunk_subdir ] [ \-t tag_subdir ] [ \-s start_chg ] [ \-m ] [ \-M regex ] <SVN_repository_URL> [ <path> ]
.SH "DESCRIPTION"
.TP
\-o <branch\-for\-HEAD>
-The trunk branch from SVN is imported to the origin branch within the git repository\&. Use this option if you want to import into a different branch\&.
+The \fItrunk\fR branch from SVN is imported to the \fIorigin\fR branch within the git repository\&. Use this option if you want to import into a different branch\&.
+
+.TP
+\-r
+Prepend \fIrX: \fR to commit messages, where X is the imported subversion revision\&.
.TP
\-m
.TP
\-v
-Verbosity: let svnimport report what it is doing\&.
+Verbosity: let \fIsvnimport\fR report what it is doing\&.
.TP
\-d
.SH "OUTPUT"
-If \-v is specified, the script reports what it is doing\&.
+If \fI\-v\fR is specified, the script reports what it is doing\&.
Otherwise, success is indicated the Unix way, i\&.e\&. by simply exiting with a zero exit status\&.