.\" 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\-CONFIG" "1" "06/08/2007" "Git 1.5.2.1.144.gabc40" "Git Manual"
+.TH "GIT\-CONFIG" "1" "06/11/2007" "Git 1.5.2.1.174.gcd03" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
Whether to include summaries of merged commits in newly created merge commit messages. False by default.
.TP
merge.tool
-Controls which merge resolution program is used by \fBgit\-mergetool\fR(l). Valid values are: "kdiff3", "tkdiff", "meld", "xxdiff", "emerge", "vimdiff", and "opendiff"
+Controls which merge resolution program is used by \fBgit\-mergetool\fR(l). Valid values are: "kdiff3", "tkdiff", "meld", "xxdiff", "emerge", "vimdiff", "gvimdiff", and "opendiff".
.TP
merge.verbosity
Controls the amount of output shown by the recursive merge strategy. Level 0 outputs nothing except a final error message if conflicts were detected. Level 1 outputs only conflicts, 2 outputs conflicts and file changes. Level 5 and above outputs debugging information. The default is level 2.
.\" 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\-MERGETOOL" "1" "06/08/2007" "Git 1.5.2.1.144.gabc40" "Git Manual"
+.TH "GIT\-MERGETOOL" "1" "06/11/2007" "Git 1.5.2.1.174.gcd03" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "OPTIONS"
.TP
\-t or \-\-tool=<tool>
-Use the merge resolution program specified by <tool>. Valid merge tools are: kdiff3, tkdiff, meld, xxdiff, emerge, vimdiff, and opendiff
+Use the merge resolution program specified by <tool>. Valid merge tools are: kdiff3, tkdiff, meld, xxdiff, emerge, vimdiff, gvimdiff, and opendiff
If a merge resolution program is not specified, \fIgit mergetool\fR will use the configuration variable merge.tool. If the configuration variable merge.tool is not set, \fIgit mergetool\fR will pick a suitable default.
.SH "AUTHOR"
.\" 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\-MKTAG" "1" "06/08/2007" "Git 1.5.2.1.144.gabc40" "Git Manual"
+.TH "GIT\-MKTAG" "1" "06/11/2007" "Git 1.5.2.1.174.gcd03" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
The output is the new tag's <object> identifier.
.SH "TAG FORMAT"
-A tag signature file has a very simple fixed format: three lines of
+A tag signature file has a very simple fixed format: four lines of
.sp
.nf
object <sha1>
type <typename>
tag <tagname>
+tagger <tagger>
.fi
-followed by some \fIoptional\fR free\-form signature that git itself doesn't care about, but that can be verified with gpg or similar.
-
-The size of the full object is artificially limited to 8kB. (Just because I'm a lazy bastard, and if you can't fit a signature in that size, you're doing something wrong)
+followed by some \fIoptional\fR free\-form message (some tags created by older git may not have tagger line). The message, when exists, is separated by a blank line from the header. The message part may contain a signature that git itself doesn't care about, but that can be verified with gpg.
.SH "AUTHOR"
Written by Linus Torvalds <torvalds@osdl.org>
.SH "DOCUMENTATION"