.\" 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/27/2007" "Git 1.5.2.2.585.g9cc0" "Git Manual"
+.TH "GIT\-CONFIG" "1" "07/02/2007" "Git 1.5.2.2.646.g71e55" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "SYNOPSIS"
.sp
.nf
-\fIgit\-config\fR [\-\-system | \-\-global] [\-z|\-\-null] name [value [value_regex]]
-\fIgit\-config\fR [\-\-system | \-\-global] \-\-add name value
-\fIgit\-config\fR [\-\-system | \-\-global] \-\-replace\-all name [value [value_regex]]
+\fIgit\-config\fR [\-\-system | \-\-global] [type] [\-z|\-\-null] name [value [value_regex]]
+\fIgit\-config\fR [\-\-system | \-\-global] [type] \-\-add name value
+\fIgit\-config\fR [\-\-system | \-\-global] [type] \-\-replace\-all name [value [value_regex]]
\fIgit\-config\fR [\-\-system | \-\-global] [type] [\-z|\-\-null] \-\-get name [value_regex]
\fIgit\-config\fR [\-\-system | \-\-global] [type] [\-z|\-\-null] \-\-get\-all name [value_regex]
\fIgit\-config\fR [\-\-system | \-\-global] [type] [\-z|\-\-null] \-\-get\-regexp name_regex [value_regex]
Multiple lines can be added to an option by using the \fI\-\-add\fR option. If you want to update or unset an option which can occur on multiple lines, a POSIX regexp value_regex needs to be given. Only the existing values that match the regexp are updated or unset. If you want to handle the lines that do \fBnot\fR match the regex, just prepend a single exclamation mark in front (see also the section called \(lqEXAMPLES\(rq).
-The type specifier can be either \fI\-\-int\fR or \fI\-\-bool\fR, which will make \fIgit\-config\fR ensure that the variable(s) are of the given type and convert the value to the canonical form (simple decimal number for int, a "true" or "false" string for bool). Type specifiers currently only take effect for reading operations. If no type specifier is passed, no checks or transformations are performed on the value.
+The type specifier can be either \fI\-\-int\fR or \fI\-\-bool\fR, which will make \fIgit\-config\fR ensure that the variable(s) are of the given type and convert the value to the canonical form (simple decimal number for int, a "true" or "false" string for bool). If no type specifier is passed, no checks or transformations are performed on the value.
This command will fail if:
.TP 3
core.fileMode
If false, the executable bit differences between the index and the working copy are ignored; useful on broken filesystems like FAT. See \fBgit\-update\-index\fR(1). True by default.
.TP
+core.quotepath
+The commands that output paths (e.g. ls\-files, diff), when not given the \-z option, will quote "unusual" characters in the pathname by enclosing the pathname in a double\-quote pair and with backslashes the same way strings in C source code are quoted. If this variable is set to false, the bytes higher than 0x80 are not quoted but output as verbatim. Note that double quote, backslash and control characters are always quoted without \-z regardless of the setting of this variable.
+.TP
core.autocrlf
If true, makes git convert CRLF at the end of lines in text files to LF when reading from the filesystem, and convert in reverse when writing to the filesystem. The variable can be set to \fIinput\fR, in which case the conversion happens only while reading from the filesystem but files are written out with LF at the end of lines. Currently, which paths to consider "text" (i.e. be subjected to the autocrlf mechanism) is decided purely based on the contents.
.TP
This setting is automatically guessed by \fBgit\-clone\fR(1) or \fBgit\-init\fR(1) when the repository was created. By default a repository that ends in "/.git" is assumed to be not bare (bare = false), while all other repositories are assumed to be bare (bare = true).
.TP
+core.worktree
+Set the path to the working tree. The value will not be used in combination with repositories found automatically in a .git directory (i.e. $GIT_DIR is not set). This can be overriden by the GIT_WORK_TREE environment variable and the \fI\-\-work\-tree\fR command line option.
+.TP
core.logAllRefUpdates
Updates to a ref <ref> is logged to the file "$GIT_DIR/logs/<ref>", by appending the new and old SHA1, the date/time and the reason of the update, but only when the file exists. If this configuration variable is set to true, missing "$GIT_DIR/logs/<ref>" file is automatically created for branch heads.
.\" 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\-DIFF\-FILES" "1" "06/16/2007" "Git 1.5.2.1.255.gca6c0" "Git Manual"
+.TH "GIT\-DIFF\-FILES" "1" "07/02/2007" "Git 1.5.2.2.646.g71e55" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.TP
3.
TAB, LF, double quote and backslash characters in pathnames are represented as \\t, \\n, \\" and \\\\, respectively. If there is need for such substitution then the whole pathname is put in double quotes.
+
+The similarity index is the percentage of unchanged lines, and the dissimilarity index is the percentage of changed lines. It is a rounded down integer, followed by a percent sign. The similarity index value of 100% is thus reserved for two equal files, while 100% dissimilarity means that no line from the old file made it into the new one.
.SH "COMBINED DIFF FORMAT"
git\-diff\-tree and git\-diff\-files can take \fI\-c\fR or \fI\-\-cc\fR option to produce \fIcombined diff\fR, which looks like this:
.sp
.\" 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\-DIFF\-INDEX" "1" "06/16/2007" "Git 1.5.2.1.255.gca6c0" "Git Manual"
+.TH "GIT\-DIFF\-INDEX" "1" "07/02/2007" "Git 1.5.2.2.646.g71e55" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.TP
3.
TAB, LF, double quote and backslash characters in pathnames are represented as \\t, \\n, \\" and \\\\, respectively. If there is need for such substitution then the whole pathname is put in double quotes.
+
+The similarity index is the percentage of unchanged lines, and the dissimilarity index is the percentage of changed lines. It is a rounded down integer, followed by a percent sign. The similarity index value of 100% is thus reserved for two equal files, while 100% dissimilarity means that no line from the old file made it into the new one.
.SH "COMBINED DIFF FORMAT"
git\-diff\-tree and git\-diff\-files can take \fI\-c\fR or \fI\-\-cc\fR option to produce \fIcombined diff\fR, which looks like this:
.sp
.\" 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\-DIFF\-TREE" "1" "06/21/2007" "Git 1.5.2.2.249.g45fd" "Git Manual"
+.TH "GIT\-DIFF\-TREE" "1" "07/02/2007" "Git 1.5.2.2.646.g71e55" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.TP
3.
TAB, LF, double quote and backslash characters in pathnames are represented as \\t, \\n, \\" and \\\\, respectively. If there is need for such substitution then the whole pathname is put in double quotes.
+
+The similarity index is the percentage of unchanged lines, and the dissimilarity index is the percentage of changed lines. It is a rounded down integer, followed by a percent sign. The similarity index value of 100% is thus reserved for two equal files, while 100% dissimilarity means that no line from the old file made it into the new one.
.SH "COMBINED DIFF FORMAT"
git\-diff\-tree and git\-diff\-files can take \fI\-c\fR or \fI\-\-cc\fR option to produce \fIcombined diff\fR, which looks like this:
.sp
.\" 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\-REV\-PARSE" "1" "06/21/2007" "Git 1.5.2.2.249.g45fd" "Git Manual"
+.TH "GIT\-REV\-PARSE" "1" "07/02/2007" "Git 1.5.2.2.646.g71e55" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
Show $GIT_DIR if defined else show the path to the .git directory.
.TP
\-\-is\-inside\-git\-dir
-Return "true" if we are in the git directory, otherwise "false". Some commands require to be run in a working directory.
+When the current working directory is below the repository directory print "true", otherwise "false".
+.TP
+\-\-is\-inside\-work\-tree
+When the current working directory is inside the work tree of the repository print "true", otherwise "false".
+.TP
+\-\-is\-bare\-repository
+When the repository is bare print "true", otherwise "false".
.TP
\-\-short, \-\-short=number
Instead of outputting the full SHA1 values of object names try to abbreviate them to a shorter unique name. When no length is specified 7 is used. The minimum length is 4.
.\" 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" "07/01/2007" "Git 1.5.2.2.619.g06f59" "Git Manual"
+.TH "GIT" "7" "07/02/2007" "Git 1.5.2.2.646.g71e55" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.sp
.nf
\fIgit\fR [\-\-version] [\-\-exec\-path[=GIT_EXEC_PATH]] [\-p|\-\-paginate]
- [\-\-bare] [\-\-git\-dir=GIT_DIR] [\-\-help] COMMAND [ARGS]
+ [\-\-bare] [\-\-git\-dir=GIT_DIR] [\-\-work\-tree=GIT_WORK_TREE]
+ [\-\-help] COMMAND [ARGS]
.fi
.SH "DESCRIPTION"
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high\-level operations and full access to internals.
\-\-git\-dir=<path>
Set the path to the repository. This can also be controlled by setting the GIT_DIR environment variable.
.TP
+\-\-work\-tree=<path>
+Set the path to the working tree. The value will not be used in combination with repositories found automatically in a .git directory (i.e. $GIT_DIR is not set). This can also be controlled by setting the GIT_WORK_TREE environment variable and the core.worktree configuration variable.
+.TP
\-\-bare
Same as \-\-git\-dir=pwd.
.SH "FURTHER DOCUMENTATION"
.TP
\fIGIT_DIR\fR
If the \fIGIT_DIR\fR environment variable is set then it specifies a path to use instead of the default .git for the base of the repository.
+.TP
+\fIGIT_WORK_TREE\fR
+Set the path to the working tree. The value will not be used in combination with repositories found automatically in a .git directory (i.e. $GIT_DIR is not set). This can also be controlled by the \fI\-\-work\-tree\fR command line option and the core.worktree configuration variable.
.SS "git Commits"
.TP
\fIGIT_AUTHOR_NAME\fR , \fIGIT_AUTHOR_EMAIL\fR , \fIGIT_AUTHOR_DATE\fR , \fIGIT_COMMITTER_NAME\fR , \fIGIT_COMMITTER_EMAIL\fR , \fIGIT_COMMITTER_DATE\fR , \fIEMAIL\fR
projects / git.git / commitdiff