.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-SEND\-EMAIL" "1" "04/26/2007" "Git 1.5.2.rc0.56.g6169a" "Git Manual"
+.TH "GIT\-SEND\-EMAIL" "1" "05/01/2007" "Git 1.5.2.rc1" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
Make git\-send\-email less verbose. One line per email should be all that is output.
.TP
\-\-smtp\-server
-If set, specifies the outgoing SMTP server to use. A full pathname of a sendmail\-like program can be specified instead; the program must support the \-i option. Default value can be specified by the \fIsendemail.smtpserver\fR configuration option; the built\-in default is /usr/sbin/sendmail or /usr/lib/sendmail if such program is available, or localhost otherwise.
+If set, specifies the outgoing SMTP server to use (e.g. smtp.example.com or a raw IP address). Alternatively it can specify a full pathname of a sendmail\-like program instead; the program must support the \-i option. Default value can be specified by the \fIsendemail.smtpserver\fR configuration option; the built\-in default is /usr/sbin/sendmail or /usr/lib/sendmail if such program is available, or localhost otherwise.
.TP
\-\-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.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-SVN" "1" "04/29/2007" "Git 1.5.2.rc0.95.ga0715" "Git Manual"
+.TH "GIT\-SVN" "1" "05/01/2007" "Git 1.5.2.rc1" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
Any other arguments are passed directly to `git log'
.TP
\fIfind\-rev\fR
-When given an SVN revision number of the form \fIrN\fR, returns the corresponding git commit hash. When given a tree\-ish, returns the corresponding SVN revision number.
+When given an SVN revision number of the form \fIrN\fR, returns the corresponding git commit hash (this can optionally be followed by a tree\-ish to specify which branch should be searched). When given a tree\-ish, returns the corresponding SVN revision number.
.TP
\fIset\-tree\fR
You should consider using \fIdcommit\fR instead of this command. Commit specified commit or tree objects to SVN. This relies on your imported fetch data being up\-to\-date. This makes absolutely no attempts to do patching when committing to SVN, it simply overwrites files with those specified in the tree or commit. All merging is assumed to have taken place independently of git\-svn functions.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT" "7" "04/29/2007" "Git 1.5.2.rc0.95.ga0715" "Git Manual"
+.TH "GIT" "7" "05/01/2007" "Git 1.5.2.rc1" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
See this [1]\&\fItutorial\fR to get started, then see [2]\&\fIEveryday Git\fR for a useful minimum set of commands, and "man git\-commandname" for documentation of each command. CVS users may also want to read [3]\&\fICVS migration\fR. [4]\&\fIGit User's Manual\fR is still work in progress, but when finished hopefully it will guide a new user in a coherent way to git enlightenment ;\-).
The COMMAND is either a name of a Git command (see below) or an alias as defined in the configuration file (see \fBgit\-config\fR(1)).
+
+Formatted and hyperlinked version of the latest git documentation can be viewed at http://www.kernel.org/pub/software/scm/git/docs/.
.SH "OPTIONS"
.TP
\-\-version