2006-04-25 00:59:33 +02:00
|
|
|
CONFIGURATION FILE
|
|
|
|
------------------
|
|
|
|
|
|
|
|
The git configuration file contains a number of variables that affect
|
2007-01-17 07:45:35 +01:00
|
|
|
the git command's behavior. `.git/config` file for each repository
|
|
|
|
is used to store the information for that repository, and
|
|
|
|
`$HOME/.gitconfig` is used to store per user information to give
|
2007-02-14 12:48:14 +01:00
|
|
|
fallback values for `.git/config` file. The file `/etc/gitconfig`
|
|
|
|
can be used to store system-wide defaults.
|
2007-01-17 07:45:35 +01:00
|
|
|
|
|
|
|
They can be used by both the git plumbing
|
2006-06-08 01:15:05 +02:00
|
|
|
and the porcelains. The variables are divided into sections, where
|
2006-04-25 00:59:33 +02:00
|
|
|
in the fully qualified variable name the variable itself is the last
|
|
|
|
dot-separated segment and the section name is everything before the last
|
|
|
|
dot. The variable names are case-insensitive and only alphanumeric
|
|
|
|
characters are allowed. Some variables may appear multiple times.
|
|
|
|
|
2007-01-22 16:25:47 +01:00
|
|
|
Syntax
|
|
|
|
~~~~~~
|
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
The syntax is fairly flexible and permissive; whitespaces are mostly
|
2007-01-22 16:25:47 +01:00
|
|
|
ignored. The '#' and ';' characters begin comments to the end of line,
|
|
|
|
blank lines are ignored.
|
|
|
|
|
|
|
|
The file consists of sections and variables. A section begins with
|
|
|
|
the name of the section in square brackets and continues until the next
|
|
|
|
section begins. Section names are not case sensitive. Only alphanumeric
|
|
|
|
characters, '`-`' and '`.`' are allowed in section names. Each variable
|
|
|
|
must belong to some section, which means that there must be section
|
|
|
|
header before first setting of a variable.
|
|
|
|
|
|
|
|
Sections can be further divided into subsections. To begin a subsection
|
|
|
|
put its name in double quotes, separated by space from the section name,
|
|
|
|
in the section header, like in example below:
|
|
|
|
|
|
|
|
--------
|
|
|
|
[section "subsection"]
|
|
|
|
|
|
|
|
--------
|
|
|
|
|
2007-01-24 15:14:33 +01:00
|
|
|
Subsection names can contain any characters except newline (doublequote
|
|
|
|
'`"`' and backslash have to be escaped as '`\"`' and '`\\`',
|
2007-02-04 05:49:16 +01:00
|
|
|
respectively) and are case sensitive. Section header cannot span multiple
|
2007-01-22 16:25:47 +01:00
|
|
|
lines. Variables may belong directly to a section or to a given subsection.
|
|
|
|
You can have `[section]` if you have `[section "subsection"]`, but you
|
|
|
|
don't need to.
|
|
|
|
|
|
|
|
There is also (case insensitive) alternative `[section.subsection]` syntax.
|
|
|
|
In this syntax subsection names follow the same restrictions as for section
|
|
|
|
name.
|
|
|
|
|
|
|
|
All the other lines are recognized as setting variables, in the form
|
|
|
|
'name = value'. If there is no equal sign on the line, the entire line
|
|
|
|
is taken as 'name' and the variable is recognized as boolean "true".
|
|
|
|
The variable names are case-insensitive and only alphanumeric
|
|
|
|
characters and '`-`' are allowed. There can be more than one value
|
|
|
|
for a given variable; we say then that variable is multivalued.
|
|
|
|
|
|
|
|
Leading and trailing whitespace in a variable value is discarded.
|
|
|
|
Internal whitespace within a variable value is retained verbatim.
|
|
|
|
|
|
|
|
The values following the equals sign in variable assign are all either
|
|
|
|
a string, an integer, or a boolean. Boolean values may be given as yes/no,
|
|
|
|
0/1 or true/false. Case is not significant in boolean values, when
|
|
|
|
converting value to the canonical form using '--bool' type specifier;
|
2007-01-29 01:16:53 +01:00
|
|
|
`git-config` will ensure that the output is "true" or "false".
|
2007-01-22 16:25:47 +01:00
|
|
|
|
|
|
|
String values may be entirely or partially enclosed in double quotes.
|
|
|
|
You need to enclose variable value in double quotes if you want to
|
|
|
|
preserve leading or trailing whitespace, or if variable value contains
|
|
|
|
beginning of comment characters (if it contains '#' or ';').
|
|
|
|
Double quote '`"`' and backslash '`\`' characters in variable value must
|
|
|
|
be escaped: use '`\"`' for '`"`' and '`\\`' for '`\`'.
|
|
|
|
|
|
|
|
The following escape sequences (beside '`\"`' and '`\\`') are recognized:
|
|
|
|
'`\n`' for newline character (NL), '`\t`' for horizontal tabulation (HT, TAB)
|
|
|
|
and '`\b`' for backspace (BS). No other char escape sequence, nor octal
|
|
|
|
char sequences are valid.
|
|
|
|
|
|
|
|
Variable value ending in a '`\`' is continued on the next line in the
|
|
|
|
customary UNIX fashion.
|
|
|
|
|
|
|
|
Some variables may require special value format.
|
2006-04-25 00:59:33 +02:00
|
|
|
|
|
|
|
Example
|
|
|
|
~~~~~~~
|
|
|
|
|
|
|
|
# Core variables
|
|
|
|
[core]
|
|
|
|
; Don't trust file modes
|
|
|
|
filemode = false
|
|
|
|
|
|
|
|
# Our diff algorithm
|
|
|
|
[diff]
|
|
|
|
external = "/usr/local/bin/gnu-diff -u"
|
|
|
|
renames = true
|
|
|
|
|
2006-12-07 07:36:55 +01:00
|
|
|
[branch "devel"]
|
|
|
|
remote = origin
|
|
|
|
merge = refs/heads/devel
|
|
|
|
|
2007-01-22 16:25:47 +01:00
|
|
|
# Proxy settings
|
|
|
|
[core]
|
2007-08-03 00:45:56 +02:00
|
|
|
gitProxy="ssh" for "kernel.org"
|
2007-01-22 16:25:47 +01:00
|
|
|
gitProxy=default-proxy ; for the rest
|
2006-12-07 07:36:55 +01:00
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
Variables
|
|
|
|
~~~~~~~~~
|
|
|
|
|
|
|
|
Note that this list is non-comprehensive and not necessarily complete.
|
2006-06-08 01:15:05 +02:00
|
|
|
For command-specific variables, you will find a more detailed description
|
|
|
|
in the appropriate manual page. You will find a description of non-core
|
2006-04-25 00:59:33 +02:00
|
|
|
porcelain configuration variables in the respective porcelain documentation.
|
|
|
|
|
|
|
|
core.fileMode::
|
|
|
|
If false, the executable bit differences between the index and
|
|
|
|
the working copy are ignored; useful on broken filesystems like FAT.
|
|
|
|
See gitlink:git-update-index[1]. True by default.
|
|
|
|
|
2007-06-25 00:11:24 +02:00
|
|
|
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.
|
|
|
|
|
2007-04-13 18:02:31 +02:00
|
|
|
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
|
|
|
|
'input', 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.
|
|
|
|
|
2007-03-02 22:11:30 +01:00
|
|
|
core.symlinks::
|
|
|
|
If false, symbolic links are checked out as small plain files that
|
|
|
|
contain the link text. gitlink:git-update-index[1] and
|
|
|
|
gitlink:git-add[1] will not change the recorded type to regular
|
|
|
|
file. Useful on filesystems like FAT that do not support
|
|
|
|
symbolic links. True by default.
|
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
core.gitProxy::
|
|
|
|
A "proxy command" to execute (as 'command host port') instead
|
|
|
|
of establishing direct connection to the remote server when
|
|
|
|
using the git protocol for fetching. If the variable value is
|
|
|
|
in the "COMMAND for DOMAIN" format, the command is applied only
|
|
|
|
on hostnames ending with the specified domain string. This variable
|
|
|
|
may be set multiple times and is matched in the given order;
|
|
|
|
the first match wins.
|
2006-06-08 01:15:05 +02:00
|
|
|
+
|
|
|
|
Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
|
|
|
|
(which always applies universally, without the special "for"
|
|
|
|
handling).
|
2006-04-25 00:59:33 +02:00
|
|
|
|
|
|
|
core.ignoreStat::
|
|
|
|
The working copy files are assumed to stay unchanged until you
|
|
|
|
mark them otherwise manually - Git will not detect the file changes
|
|
|
|
by lstat() calls. This is useful on systems where those are very
|
|
|
|
slow, such as Microsoft Windows. See gitlink:git-update-index[1].
|
|
|
|
False by default.
|
|
|
|
|
2006-05-02 09:40:24 +02:00
|
|
|
core.preferSymlinkRefs::
|
|
|
|
Instead of the default "symref" format for HEAD
|
|
|
|
and other symbolic reference files, use symbolic links.
|
|
|
|
This is sometimes needed to work with old scripts that
|
|
|
|
expect HEAD to be a symbolic link.
|
2006-04-25 00:59:33 +02:00
|
|
|
|
2007-02-21 23:59:08 +01:00
|
|
|
core.bare::
|
|
|
|
If true this repository is assumed to be 'bare' and has no
|
|
|
|
working directory associated with it. If this is the case a
|
|
|
|
number of commands that require a working directory will be
|
|
|
|
disabled, such as gitlink:git-add[1] or gitlink:git-merge[1].
|
|
|
|
+
|
|
|
|
This setting is automatically guessed by gitlink:git-clone[1] or
|
|
|
|
gitlink:git-init[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).
|
|
|
|
|
2007-06-06 09:10:42 +02:00
|
|
|
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).
|
2007-10-09 23:00:03 +02:00
|
|
|
This can be overridden by the GIT_WORK_TREE environment
|
2007-06-06 09:10:42 +02:00
|
|
|
variable and the '--work-tree' command line option.
|
|
|
|
|
2006-05-17 11:55:40 +02:00
|
|
|
core.logAllRefUpdates::
|
2007-08-19 23:38:57 +02:00
|
|
|
Enable the reflog. Updates to a ref <ref> is logged to the file
|
2006-10-08 10:35:18 +02:00
|
|
|
"$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.
|
2006-12-31 07:39:24 +01:00
|
|
|
+
|
|
|
|
This information can be used to determine what commit
|
|
|
|
was the tip of a branch "2 days ago".
|
|
|
|
+
|
|
|
|
This value is true by default in a repository that has
|
|
|
|
a working directory associated with it, and false by
|
|
|
|
default in a bare repository.
|
2006-05-17 11:55:40 +02:00
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
core.repositoryFormatVersion::
|
|
|
|
Internal variable identifying the repository format and layout
|
|
|
|
version.
|
|
|
|
|
|
|
|
core.sharedRepository::
|
2006-08-09 02:26:23 +02:00
|
|
|
When 'group' (or 'true'), the repository is made shareable between
|
|
|
|
several users in a group (making sure all the files and objects are
|
|
|
|
group-writable). When 'all' (or 'world' or 'everybody'), the
|
|
|
|
repository will be readable by all users, additionally to being
|
|
|
|
group-shareable. When 'umask' (or 'false'), git will use permissions
|
2007-01-12 22:01:46 +01:00
|
|
|
reported by umask(2). See gitlink:git-init[1]. False by default.
|
2006-04-25 00:59:33 +02:00
|
|
|
|
|
|
|
core.warnAmbiguousRefs::
|
|
|
|
If true, git will warn you if the ref name you passed it is ambiguous
|
|
|
|
and might match multiple refs in the .git/refs/ tree. True by default.
|
|
|
|
|
2006-07-06 22:35:54 +02:00
|
|
|
core.compression::
|
Custom compression levels for objects and packs
Add config variables pack.compression and core.loosecompression ,
and switch --compression=level to pack-objects.
Loose objects will be compressed using core.loosecompression if set,
else core.compression if set, else Z_BEST_SPEED.
Packed objects will be compressed using --compression=level if seen,
else pack.compression if set, else core.compression if set,
else Z_DEFAULT_COMPRESSION. This is the "pack compression level".
Loose objects added to a pack undeltified will be recompressed
to the pack compression level if it is unequal to the current
loose compression level by the preceding rules, or if the loose
object was written while core.legacyheaders = true. Newly
deltified loose objects are always compressed to the current
pack compression level.
Previously packed objects added to a pack are recompressed
to the current pack compression level exactly when their
deltification status changes, since the previous pack data
cannot be reused.
In either case, the --no-reuse-object switch from the first
patch below will always force recompression to the current pack
compression level, instead of assuming the pack compression level
hasn't changed and pack data can be reused when possible.
This applies on top of the following patches from Nicolas Pitre:
[PATCH] allow for undeltified objects not to be reused
[PATCH] make "repack -f" imply "pack-objects --no-reuse-object"
Signed-off-by: Dana L. How <danahow@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-05-09 22:56:50 +02:00
|
|
|
An integer -1..9, indicating a default compression level.
|
|
|
|
-1 is the zlib default. 0 means no compression,
|
|
|
|
and 1..9 are various speed/size tradeoffs, 9 being slowest.
|
2007-11-19 17:58:51 +01:00
|
|
|
If set, this provides a default to other compression variables,
|
|
|
|
such as 'core.loosecompression' and 'pack.compression'.
|
Custom compression levels for objects and packs
Add config variables pack.compression and core.loosecompression ,
and switch --compression=level to pack-objects.
Loose objects will be compressed using core.loosecompression if set,
else core.compression if set, else Z_BEST_SPEED.
Packed objects will be compressed using --compression=level if seen,
else pack.compression if set, else core.compression if set,
else Z_DEFAULT_COMPRESSION. This is the "pack compression level".
Loose objects added to a pack undeltified will be recompressed
to the pack compression level if it is unequal to the current
loose compression level by the preceding rules, or if the loose
object was written while core.legacyheaders = true. Newly
deltified loose objects are always compressed to the current
pack compression level.
Previously packed objects added to a pack are recompressed
to the current pack compression level exactly when their
deltification status changes, since the previous pack data
cannot be reused.
In either case, the --no-reuse-object switch from the first
patch below will always force recompression to the current pack
compression level, instead of assuming the pack compression level
hasn't changed and pack data can be reused when possible.
This applies on top of the following patches from Nicolas Pitre:
[PATCH] allow for undeltified objects not to be reused
[PATCH] make "repack -f" imply "pack-objects --no-reuse-object"
Signed-off-by: Dana L. How <danahow@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-05-09 22:56:50 +02:00
|
|
|
|
|
|
|
core.loosecompression::
|
2006-07-03 22:11:47 +02:00
|
|
|
An integer -1..9, indicating the compression level for objects that
|
Custom compression levels for objects and packs
Add config variables pack.compression and core.loosecompression ,
and switch --compression=level to pack-objects.
Loose objects will be compressed using core.loosecompression if set,
else core.compression if set, else Z_BEST_SPEED.
Packed objects will be compressed using --compression=level if seen,
else pack.compression if set, else core.compression if set,
else Z_DEFAULT_COMPRESSION. This is the "pack compression level".
Loose objects added to a pack undeltified will be recompressed
to the pack compression level if it is unequal to the current
loose compression level by the preceding rules, or if the loose
object was written while core.legacyheaders = true. Newly
deltified loose objects are always compressed to the current
pack compression level.
Previously packed objects added to a pack are recompressed
to the current pack compression level exactly when their
deltification status changes, since the previous pack data
cannot be reused.
In either case, the --no-reuse-object switch from the first
patch below will always force recompression to the current pack
compression level, instead of assuming the pack compression level
hasn't changed and pack data can be reused when possible.
This applies on top of the following patches from Nicolas Pitre:
[PATCH] allow for undeltified objects not to be reused
[PATCH] make "repack -f" imply "pack-objects --no-reuse-object"
Signed-off-by: Dana L. How <danahow@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-05-09 22:56:50 +02:00
|
|
|
are not in a pack file. -1 is the zlib default. 0 means no
|
2006-07-03 22:11:47 +02:00
|
|
|
compression, and 1..9 are various speed/size tradeoffs, 9 being
|
Custom compression levels for objects and packs
Add config variables pack.compression and core.loosecompression ,
and switch --compression=level to pack-objects.
Loose objects will be compressed using core.loosecompression if set,
else core.compression if set, else Z_BEST_SPEED.
Packed objects will be compressed using --compression=level if seen,
else pack.compression if set, else core.compression if set,
else Z_DEFAULT_COMPRESSION. This is the "pack compression level".
Loose objects added to a pack undeltified will be recompressed
to the pack compression level if it is unequal to the current
loose compression level by the preceding rules, or if the loose
object was written while core.legacyheaders = true. Newly
deltified loose objects are always compressed to the current
pack compression level.
Previously packed objects added to a pack are recompressed
to the current pack compression level exactly when their
deltification status changes, since the previous pack data
cannot be reused.
In either case, the --no-reuse-object switch from the first
patch below will always force recompression to the current pack
compression level, instead of assuming the pack compression level
hasn't changed and pack data can be reused when possible.
This applies on top of the following patches from Nicolas Pitre:
[PATCH] allow for undeltified objects not to be reused
[PATCH] make "repack -f" imply "pack-objects --no-reuse-object"
Signed-off-by: Dana L. How <danahow@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-05-09 22:56:50 +02:00
|
|
|
slowest. If not set, defaults to core.compression. If that is
|
2007-11-19 17:58:50 +01:00
|
|
|
not set, defaults to 1 (best speed).
|
2006-07-03 22:11:47 +02:00
|
|
|
|
2006-12-23 08:34:28 +01:00
|
|
|
core.packedGitWindowSize::
|
|
|
|
Number of bytes of a pack file to map into memory in a
|
|
|
|
single mapping operation. Larger window sizes may allow
|
|
|
|
your system to process a smaller number of large pack files
|
|
|
|
more quickly. Smaller window sizes will negatively affect
|
2006-12-31 04:13:43 +01:00
|
|
|
performance due to increased calls to the operating system's
|
2006-12-23 08:34:28 +01:00
|
|
|
memory manager, but may improve performance when accessing
|
2007-01-05 04:28:08 +01:00
|
|
|
a large number of large pack files.
|
|
|
|
+
|
|
|
|
Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
|
|
|
|
MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should
|
|
|
|
be reasonable for all users/operating systems. You probably do
|
|
|
|
not need to adjust this value.
|
2006-12-31 04:13:43 +01:00
|
|
|
+
|
|
|
|
Common unit suffixes of 'k', 'm', or 'g' are supported.
|
2006-12-23 08:34:28 +01:00
|
|
|
|
2006-12-23 08:33:35 +01:00
|
|
|
core.packedGitLimit::
|
|
|
|
Maximum number of bytes to map simultaneously into memory
|
|
|
|
from pack files. If Git needs to access more than this many
|
|
|
|
bytes at once to complete an operation it will unmap existing
|
|
|
|
regions to reclaim virtual address space within the process.
|
2007-01-05 04:28:08 +01:00
|
|
|
+
|
|
|
|
Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
|
|
|
|
This should be reasonable for all users/operating systems, except on
|
|
|
|
the largest projects. You probably do not need to adjust this value.
|
2006-12-31 04:13:43 +01:00
|
|
|
+
|
|
|
|
Common unit suffixes of 'k', 'm', or 'g' are supported.
|
2006-12-23 08:33:35 +01:00
|
|
|
|
2007-03-19 06:14:37 +01:00
|
|
|
core.deltaBaseCacheLimit::
|
|
|
|
Maximum number of bytes to reserve for caching base objects
|
|
|
|
that multiple deltafied objects reference. By storing the
|
|
|
|
entire decompressed base objects in a cache Git is able
|
|
|
|
to avoid unpacking and decompressing frequently used base
|
|
|
|
objects multiple times.
|
|
|
|
+
|
|
|
|
Default is 16 MiB on all platforms. This should be reasonable
|
|
|
|
for all users/operating systems, except on the largest projects.
|
|
|
|
You probably do not need to adjust this value.
|
|
|
|
+
|
|
|
|
Common unit suffixes of 'k', 'm', or 'g' are supported.
|
|
|
|
|
2007-07-02 18:48:34 +02:00
|
|
|
core.excludesfile::
|
2007-05-22 02:12:17 +02:00
|
|
|
In addition to '.gitignore' (per-directory) and
|
|
|
|
'.git/info/exclude', git looks into this file for patterns
|
2007-06-02 19:08:54 +02:00
|
|
|
of files which are not meant to be tracked. See
|
|
|
|
gitlink:gitignore[5].
|
2007-05-22 02:12:17 +02:00
|
|
|
|
2007-07-20 07:09:35 +02:00
|
|
|
core.editor::
|
|
|
|
Commands such as `commit` and `tag` that lets you edit
|
2007-08-24 02:44:13 +02:00
|
|
|
messages by launching an editor uses the value of this
|
2007-07-20 07:09:35 +02:00
|
|
|
variable when it is set, and the environment variable
|
|
|
|
`GIT_EDITOR` is not set. The order of preference is
|
2007-07-22 07:37:56 +02:00
|
|
|
`GIT_EDITOR` environment, `core.editor`, `VISUAL` and
|
|
|
|
`EDITOR` environment variables and then finally `vi`.
|
2007-07-20 07:09:35 +02:00
|
|
|
|
2007-07-03 20:18:11 +02:00
|
|
|
core.pager::
|
|
|
|
The command that git will use to paginate output. Can be overridden
|
|
|
|
with the `GIT_PAGER` environment variable.
|
|
|
|
|
2006-06-07 20:43:50 +02:00
|
|
|
alias.*::
|
|
|
|
Command aliases for the gitlink:git[1] command wrapper - e.g.
|
|
|
|
after defining "alias.last = cat-file commit HEAD", the invocation
|
|
|
|
"git last" is equivalent to "git cat-file commit HEAD". To avoid
|
2006-06-08 02:25:21 +02:00
|
|
|
confusion and troubles with script usage, aliases that
|
|
|
|
hide existing git commands are ignored. Arguments are split by
|
|
|
|
spaces, the usual shell quoting and escaping is supported.
|
|
|
|
quote pair and a backslash can be used to quote them.
|
2007-09-01 13:01:54 +02:00
|
|
|
+
|
|
|
|
If the alias expansion is prefixed with an exclamation point,
|
|
|
|
it will be treated as a shell command. For example, defining
|
|
|
|
"alias.new = !gitk --all --not ORIG_HEAD", the invocation
|
|
|
|
"git new" is equivalent to running the shell command
|
|
|
|
"gitk --all --not ORIG_HEAD".
|
2007-02-11 01:33:58 +01:00
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
apply.whitespace::
|
|
|
|
Tells `git-apply` how to handle whitespaces, in the same way
|
|
|
|
as the '--whitespace' option. See gitlink:git-apply[1].
|
|
|
|
|
2007-05-23 07:07:54 +02:00
|
|
|
branch.autosetupmerge::
|
2007-05-24 00:16:12 +02:00
|
|
|
Tells `git-branch` and `git-checkout` to setup new branches
|
2007-05-23 07:07:54 +02:00
|
|
|
so that gitlink:git-pull[1] will appropriately merge from that
|
|
|
|
remote branch. Note that even if this option is not set,
|
|
|
|
this behavior can be chosen per-branch using the `--track`
|
2007-07-10 19:50:44 +02:00
|
|
|
and `--no-track` options. This option defaults to false.
|
2007-05-23 07:07:54 +02:00
|
|
|
|
2006-09-23 12:05:43 +02:00
|
|
|
branch.<name>.remote::
|
|
|
|
When in branch <name>, it tells `git fetch` which remote to fetch.
|
2006-12-09 02:28:26 +01:00
|
|
|
If this option is not given, `git fetch` defaults to remote "origin".
|
2006-09-23 12:05:43 +02:00
|
|
|
|
2006-09-23 22:53:04 +02:00
|
|
|
branch.<name>.merge::
|
2007-09-11 05:03:25 +02:00
|
|
|
When in branch <name>, it tells `git fetch` the default
|
|
|
|
refspec to be marked for merging in FETCH_HEAD. The value is
|
|
|
|
handled like the remote part of a refspec, and must match a
|
|
|
|
ref which is fetched from the remote given by
|
|
|
|
"branch.<name>.remote".
|
2006-12-09 02:28:26 +01:00
|
|
|
The merge information is used by `git pull` (which at first calls
|
|
|
|
`git fetch`) to lookup the default branch for merging. Without
|
|
|
|
this option, `git pull` defaults to merge the first refspec fetched.
|
|
|
|
Specify multiple values to get an octopus merge.
|
git-fetch, git-branch: Support local --track via a special remote '.'
This patch adds support for a dummy remote '.' to avoid having
to declare a fake remote like
[remote "local"]
url = .
fetch = refs/heads/*:refs/heads/*
Such a builtin remote simplifies the operation of "git-fetch",
which will populate FETCH_HEAD but will not pretend that two
repositories are in use, will not create a thin pack, and will
not perform any useless remapping of names. The speed
improvement is around 20%, and it should improve more if
"git-fetch" is converted to a builtin.
To this end, git-parse-remote is grown with a new kind of
remote, 'builtin'. In git-fetch.sh, we treat the builtin remote
specially in that it needs no pack/store operations. In fact,
doing git-fetch on a builtin remote will simply populate
FETCH_HEAD appropriately.
The patch also improves of the --track/--no-track support,
extending it so that branch.<name>.remote items referring '.'
can be created. Finally, it fixes a typo in git-checkout.sh.
Signed-off-by: Paolo Bonzini <bonzini@gnu.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-03-15 09:23:20 +01:00
|
|
|
If you wish to setup `git pull` so that it merges into <name> from
|
|
|
|
another branch in the local repository, you can point
|
|
|
|
branch.<name>.merge to the desired branch, and use the special setting
|
|
|
|
`.` (a period) for branch.<name>.remote.
|
2006-09-23 22:53:04 +02:00
|
|
|
|
2007-09-24 00:51:43 +02:00
|
|
|
branch.<name>.mergeoptions::
|
|
|
|
Sets default options for merging into branch <name>. The syntax and
|
|
|
|
supported options are equal to that of gitlink:git-merge[1], but
|
|
|
|
option values containing whitespace characters are currently not
|
|
|
|
supported.
|
|
|
|
|
2007-11-28 14:11:07 +01:00
|
|
|
branch.<name>.rebase::
|
|
|
|
When true, rebase the branch <name> on top of the fetched branch,
|
|
|
|
instead of merging the default branch from the default remote.
|
|
|
|
*NOTE*: this is a possibly dangerous operation; do *not* use
|
|
|
|
it unless you understand the implications (see gitlink:git-rebase[1]
|
|
|
|
for details).
|
|
|
|
|
2007-04-24 02:18:16 +02:00
|
|
|
clean.requireForce::
|
2007-11-02 01:32:04 +01:00
|
|
|
A boolean to make git-clean do nothing unless given -f
|
|
|
|
or -n. Defaults to true.
|
2007-04-24 02:18:16 +02:00
|
|
|
|
2007-01-03 16:36:29 +01:00
|
|
|
color.branch::
|
|
|
|
A boolean to enable/disable color in the output of
|
2007-12-06 02:05:17 +01:00
|
|
|
gitlink:git-branch[1]. May be set to `always`,
|
|
|
|
`false` (or `never`) or `auto` (or `true`), in which case colors are used
|
2007-01-03 16:36:29 +01:00
|
|
|
only when the output is to a terminal. Defaults to false.
|
|
|
|
|
|
|
|
color.branch.<slot>::
|
|
|
|
Use customized color for branch coloration. `<slot>` is one of
|
|
|
|
`current` (the current branch), `local` (a local branch),
|
|
|
|
`remote` (a tracking branch in refs/remotes/), `plain` (other
|
2007-01-28 16:17:36 +01:00
|
|
|
refs).
|
|
|
|
+
|
|
|
|
The value for these configuration variables is a list of colors (at most
|
|
|
|
two) and attributes (at most one), separated by spaces. The colors
|
|
|
|
accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
|
|
|
|
`magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
|
|
|
|
`blink` and `reverse`. The first color given is the foreground; the
|
|
|
|
second is the background. The position of the attribute, if any,
|
|
|
|
doesn't matter.
|
2007-01-03 16:36:29 +01:00
|
|
|
|
2006-12-13 10:13:28 +01:00
|
|
|
color.diff::
|
2007-12-06 02:05:17 +01:00
|
|
|
When set to `always`, always use colors in patch.
|
|
|
|
When false (or `never`), never. When set to `true` or `auto`, use
|
|
|
|
colors only when the output is to the terminal. Defaults to false.
|
2006-07-07 14:28:05 +02:00
|
|
|
|
2006-12-13 10:13:28 +01:00
|
|
|
color.diff.<slot>::
|
2007-01-28 16:17:36 +01:00
|
|
|
Use customized color for diff colorization. `<slot>` specifies
|
|
|
|
which part of the patch to use the specified color, and is one
|
|
|
|
of `plain` (context text), `meta` (metainformation), `frag`
|
|
|
|
(hunk header), `old` (removed lines), `new` (added lines),
|
|
|
|
`commit` (commit headers), or `whitespace` (highlighting dubious
|
|
|
|
whitespace). The values of these variables may be specified as
|
|
|
|
in color.branch.<slot>.
|
2006-07-07 14:28:05 +02:00
|
|
|
|
2007-12-05 09:50:23 +01:00
|
|
|
color.interactive::
|
|
|
|
When set to `always`, always use colors in `git add --interactive`.
|
|
|
|
When false (or `never`), never. When set to `true` or `auto`, use
|
|
|
|
colors only when the output is to the terminal. Defaults to false.
|
|
|
|
|
|
|
|
color.interactive.<slot>::
|
|
|
|
Use customized color for `git add --interactive`
|
|
|
|
output. `<slot>` may be `prompt`, `header`, or `help`, for
|
|
|
|
three distinct types of normal output from interactive
|
|
|
|
programs. The values of these variables may be specified as
|
|
|
|
in color.branch.<slot>.
|
|
|
|
|
2006-12-13 21:11:03 +01:00
|
|
|
color.pager::
|
|
|
|
A boolean to enable/disable colored output when the pager is in
|
|
|
|
use (default is true).
|
|
|
|
|
|
|
|
color.status::
|
|
|
|
A boolean to enable/disable color in the output of
|
2007-12-06 02:05:17 +01:00
|
|
|
gitlink:git-status[1]. May be set to `always`,
|
|
|
|
`false` (or `never`) or `auto` (or `true`), in which case colors are used
|
2006-12-13 21:11:03 +01:00
|
|
|
only when the output is to a terminal. Defaults to false.
|
|
|
|
|
|
|
|
color.status.<slot>::
|
|
|
|
Use customized color for status colorization. `<slot>` is
|
|
|
|
one of `header` (the header text of the status message),
|
2006-12-16 03:53:13 +01:00
|
|
|
`added` or `updated` (files which are added but not committed),
|
|
|
|
`changed` (files which are changed but not added in the index),
|
2006-12-13 21:11:03 +01:00
|
|
|
or `untracked` (files which are not tracked by git). The values of
|
2007-01-03 16:36:29 +01:00
|
|
|
these variables may be specified as in color.branch.<slot>.
|
2006-12-13 21:11:03 +01:00
|
|
|
|
2007-07-26 22:34:59 +02:00
|
|
|
commit.template::
|
|
|
|
Specify a file to use as the template for new commit messages.
|
|
|
|
|
2007-08-31 22:13:42 +02:00
|
|
|
diff.autorefreshindex::
|
|
|
|
When using `git diff` to compare with work tree
|
|
|
|
files, do not consider stat-only change as changed.
|
|
|
|
Instead, silently run `git update-index --refresh` to
|
|
|
|
update the cached stat information for paths whose
|
|
|
|
contents in the work tree match the contents in the
|
|
|
|
index. This option defaults to true. Note that this
|
|
|
|
affects only `git diff` Porcelain, and not lower level
|
|
|
|
`diff` commands, such as `git diff-files`.
|
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
diff.renameLimit::
|
|
|
|
The number of files to consider when performing the copy/rename
|
|
|
|
detection; equivalent to the git diff option '-l'.
|
|
|
|
|
2006-07-07 13:01:23 +02:00
|
|
|
diff.renames::
|
|
|
|
Tells git to detect renames. If set to any boolean value, it
|
|
|
|
will enable basic rename detection. If set to "copies" or
|
|
|
|
"copy", it will detect copies, as well.
|
|
|
|
|
2007-01-25 01:47:24 +01:00
|
|
|
fetch.unpackLimit::
|
|
|
|
If the number of objects fetched over the git native
|
|
|
|
transfer is below this
|
|
|
|
limit, then the objects will be unpacked into loose object
|
|
|
|
files. However if the number of received objects equals or
|
|
|
|
exceeds this limit then the received pack will be stored as
|
|
|
|
a pack, after adding any missing delta bases. Storing the
|
|
|
|
pack from a push can make the push operation complete faster,
|
|
|
|
especially on slow filesystems.
|
|
|
|
|
2007-11-04 04:38:24 +01:00
|
|
|
format.numbered::
|
|
|
|
A boolean which can enable sequence numbers in patch subjects.
|
|
|
|
Seting this option to "auto" will enable it only if there is
|
|
|
|
more than one patch. See --numbered option in
|
|
|
|
gitlink:git-format-patch[1].
|
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
format.headers::
|
|
|
|
Additional email headers to include in a patch to be submitted
|
|
|
|
by mail. See gitlink:git-format-patch[1].
|
|
|
|
|
2007-03-04 00:17:23 +01:00
|
|
|
format.suffix::
|
|
|
|
The default for format-patch is to output files with the suffix
|
|
|
|
`.patch`. Use this variable to change that suffix (make sure to
|
|
|
|
include the dot if you want it).
|
2006-04-25 00:59:33 +02:00
|
|
|
|
2007-05-09 21:48:39 +02:00
|
|
|
gc.aggressiveWindow::
|
|
|
|
The window size parameter used in the delta compression
|
|
|
|
algorithm used by 'git gc --aggressive'. This defaults
|
|
|
|
to 10.
|
|
|
|
|
2007-09-17 09:39:52 +02:00
|
|
|
gc.auto::
|
|
|
|
When there are approximately more than this many loose
|
|
|
|
objects in the repository, `git gc --auto` will pack them.
|
|
|
|
Some Porcelain commands use this command to perform a
|
|
|
|
light-weight garbage collection from time to time. Setting
|
|
|
|
this to 0 disables it.
|
|
|
|
|
2007-09-17 09:55:13 +02:00
|
|
|
gc.autopacklimit::
|
|
|
|
When there are more than this many packs that are not
|
|
|
|
marked with `*.keep` file in the repository, `git gc
|
|
|
|
--auto` consolidates them into one larger pack. Setting
|
|
|
|
this to 0 disables this.
|
|
|
|
|
2007-02-13 14:01:42 +01:00
|
|
|
gc.packrefs::
|
|
|
|
`git gc` does not run `git pack-refs` in a bare repository by
|
|
|
|
default so that older dumb-transport clients can still fetch
|
|
|
|
from the repository. Setting this to `true` lets `git
|
|
|
|
gc` to run `git pack-refs`. Setting this to `false` tells
|
|
|
|
`git gc` never to run `git pack-refs`. The default setting is
|
|
|
|
`notbare`. Enable it only when you know you do not have to
|
|
|
|
support such clients. The default setting will change to `true`
|
|
|
|
at some stage, and setting this to `false` will continue to
|
|
|
|
prevent `git pack-refs` from being run from `git gc`.
|
|
|
|
|
2006-12-27 10:47:57 +01:00
|
|
|
gc.reflogexpire::
|
|
|
|
`git reflog expire` removes reflog entries older than
|
|
|
|
this time; defaults to 90 days.
|
|
|
|
|
|
|
|
gc.reflogexpireunreachable::
|
|
|
|
`git reflog expire` removes reflog entries older than
|
|
|
|
this time and are not reachable from the current tip;
|
|
|
|
defaults to 30 days.
|
|
|
|
|
2006-12-27 10:24:05 +01:00
|
|
|
gc.rerereresolved::
|
|
|
|
Records of conflicted merge you resolved earlier are
|
|
|
|
kept for this many days when `git rerere gc` is run.
|
|
|
|
The default is 60 days. See gitlink:git-rerere[1].
|
|
|
|
|
|
|
|
gc.rerereunresolved::
|
|
|
|
Records of conflicted merge you have not resolved are
|
|
|
|
kept for this many days when `git rerere gc` is run.
|
|
|
|
The default is 15 days. See gitlink:git-rerere[1].
|
|
|
|
|
2007-07-06 14:05:59 +02:00
|
|
|
rerere.enabled::
|
|
|
|
Activate recording of resolved conflicts, so that identical
|
|
|
|
conflict hunks can be resolved automatically, should they
|
2007-12-04 09:40:55 +01:00
|
|
|
be encountered again. gitlink:git-rerere[1] command is by
|
|
|
|
default enabled, but can be disabled by setting this option to
|
|
|
|
false.
|
2007-07-06 14:05:59 +02:00
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
gitcvs.enabled::
|
2007-08-24 02:40:08 +02:00
|
|
|
Whether the CVS server interface is enabled for this repository.
|
2006-04-25 00:59:33 +02:00
|
|
|
See gitlink:git-cvsserver[1].
|
|
|
|
|
|
|
|
gitcvs.logfile::
|
2007-08-24 02:40:08 +02:00
|
|
|
Path to a log file where the CVS server interface well... logs
|
2006-04-25 00:59:33 +02:00
|
|
|
various stuff. See gitlink:git-cvsserver[1].
|
|
|
|
|
2007-04-13 18:02:30 +02:00
|
|
|
gitcvs.allbinary::
|
|
|
|
If true, all files are sent to the client in mode '-kb'. This
|
|
|
|
causes the client to treat all files as binary files which suppresses
|
|
|
|
any newline munging it otherwise might do. A work-around for the
|
|
|
|
fact that there is no way yet to set single files to mode '-kb'.
|
2007-04-18 07:17:46 +02:00
|
|
|
|
2007-04-13 18:13:42 +02:00
|
|
|
gitcvs.dbname::
|
|
|
|
Database used by git-cvsserver to cache revision information
|
|
|
|
derived from the git repository. The exact meaning depends on the
|
|
|
|
used database driver, for SQLite (which is the default driver) this
|
|
|
|
is a filename. Supports variable substitution (see
|
|
|
|
gitlink:git-cvsserver[1] for details). May not contain semicolons (`;`).
|
|
|
|
Default: '%Ggitcvs.%m.sqlite'
|
|
|
|
|
|
|
|
gitcvs.dbdriver::
|
|
|
|
Used Perl DBI driver. You can specify any available driver
|
|
|
|
for this here, but it might not work. git-cvsserver is tested
|
|
|
|
with 'DBD::SQLite', reported to work with 'DBD::Pg', and
|
|
|
|
reported *not* to work with 'DBD::mysql'. Experimental feature.
|
|
|
|
May not contain double colons (`:`). Default: 'SQLite'.
|
2007-04-13 18:02:30 +02:00
|
|
|
See gitlink:git-cvsserver[1].
|
|
|
|
|
2007-04-13 18:13:42 +02:00
|
|
|
gitcvs.dbuser, gitcvs.dbpass::
|
|
|
|
Database user and password. Only useful if setting 'gitcvs.dbdriver',
|
|
|
|
since SQLite has no concept of database users and/or passwords.
|
|
|
|
'gitcvs.dbuser' supports variable substitution (see
|
|
|
|
gitlink:git-cvsserver[1] for details).
|
|
|
|
|
2007-08-24 02:44:13 +02:00
|
|
|
All gitcvs variables except for 'gitcvs.allbinary' can also be
|
|
|
|
specified as 'gitcvs.<access_method>.<varname>' (where 'access_method'
|
|
|
|
is one of "ext" and "pserver") to make them apply only for the given
|
|
|
|
access method.
|
2007-04-13 18:13:42 +02:00
|
|
|
|
2007-11-23 01:07:00 +01:00
|
|
|
http.proxy::
|
|
|
|
Override the HTTP proxy, normally configured using the 'http_proxy'
|
2007-12-03 22:48:54 +01:00
|
|
|
environment variable (see gitlink:curl[1]). This can be overridden
|
|
|
|
on a per-remote basis; see remote.<name>.proxy
|
2007-11-23 01:07:00 +01:00
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
http.sslVerify::
|
|
|
|
Whether to verify the SSL certificate when fetching or pushing
|
2006-06-07 14:56:45 +02:00
|
|
|
over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
|
2006-04-25 00:59:33 +02:00
|
|
|
variable.
|
|
|
|
|
|
|
|
http.sslCert::
|
|
|
|
File containing the SSL certificate when fetching or pushing
|
2006-06-07 14:56:45 +02:00
|
|
|
over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
|
2006-04-25 00:59:33 +02:00
|
|
|
variable.
|
|
|
|
|
|
|
|
http.sslKey::
|
|
|
|
File containing the SSL private key when fetching or pushing
|
2006-06-03 22:27:26 +02:00
|
|
|
over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
|
2006-04-25 00:59:33 +02:00
|
|
|
variable.
|
|
|
|
|
|
|
|
http.sslCAInfo::
|
|
|
|
File containing the certificates to verify the peer with when
|
2006-06-03 22:27:26 +02:00
|
|
|
fetching or pushing over HTTPS. Can be overridden by the
|
2006-04-25 00:59:33 +02:00
|
|
|
'GIT_SSL_CAINFO' environment variable.
|
|
|
|
|
|
|
|
http.sslCAPath::
|
|
|
|
Path containing files with the CA certificates to verify the peer
|
2006-06-07 14:56:45 +02:00
|
|
|
with when fetching or pushing over HTTPS. Can be overridden
|
2006-04-25 00:59:33 +02:00
|
|
|
by the 'GIT_SSL_CAPATH' environment variable.
|
|
|
|
|
|
|
|
http.maxRequests::
|
2006-06-03 22:27:26 +02:00
|
|
|
How many HTTP requests to launch in parallel. Can be overridden
|
2006-04-25 00:59:33 +02:00
|
|
|
by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
|
|
|
|
|
|
|
|
http.lowSpeedLimit, http.lowSpeedTime::
|
|
|
|
If the HTTP transfer speed is less than 'http.lowSpeedLimit'
|
|
|
|
for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
|
2006-06-03 22:27:26 +02:00
|
|
|
Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
|
2006-04-25 00:59:33 +02:00
|
|
|
'GIT_HTTP_LOW_SPEED_TIME' environment variables.
|
|
|
|
|
2006-09-29 02:10:44 +02:00
|
|
|
http.noEPSV::
|
|
|
|
A boolean which disables using of EPSV ftp command by curl.
|
2007-04-13 18:02:33 +02:00
|
|
|
This can helpful with some "poor" ftp servers which don't
|
2006-09-29 02:10:44 +02:00
|
|
|
support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
|
|
|
|
environment variable. Default is false (curl will use EPSV).
|
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
i18n.commitEncoding::
|
|
|
|
Character encoding the commit messages are stored in; git itself
|
|
|
|
does not care per se, but this information is necessary e.g. when
|
|
|
|
importing commits from emails or in the gitk graphical history
|
|
|
|
browser (and possibly at other places in the future or in other
|
|
|
|
porcelains). See e.g. gitlink:git-mailinfo[1]. Defaults to 'utf-8'.
|
|
|
|
|
2006-12-28 01:41:33 +01:00
|
|
|
i18n.logOutputEncoding::
|
|
|
|
Character encoding the commit messages are converted to when
|
|
|
|
running `git-log` and friends.
|
|
|
|
|
2006-11-23 10:36:33 +01:00
|
|
|
log.showroot::
|
|
|
|
If true, the initial commit will be shown as a big creation event.
|
|
|
|
This is equivalent to a diff against an empty tree.
|
|
|
|
Tools like gitlink:git-log[1] or gitlink:git-whatchanged[1], which
|
|
|
|
normally hide the root commit will now show it. True by default.
|
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
merge.summary::
|
|
|
|
Whether to include summaries of merged commits in newly created
|
|
|
|
merge commit messages. False by default.
|
|
|
|
|
2007-03-06 06:05:16 +01:00
|
|
|
merge.tool::
|
|
|
|
Controls which merge resolution program is used by
|
2007-10-02 22:14:30 +02:00
|
|
|
gitlink:git-mergetool[1]. Valid values are: "kdiff3", "tkdiff",
|
2007-06-06 03:19:47 +02:00
|
|
|
"meld", "xxdiff", "emerge", "vimdiff", "gvimdiff", and "opendiff".
|
2007-03-06 06:05:16 +01:00
|
|
|
|
2007-01-14 06:28:48 +01:00
|
|
|
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.
|
2007-10-09 23:00:03 +02:00
|
|
|
Can be overridden by 'GIT_MERGE_VERBOSITY' environment variable.
|
2007-01-14 06:28:48 +01:00
|
|
|
|
2007-04-20 05:48:03 +02:00
|
|
|
merge.<driver>.name::
|
|
|
|
Defines a human readable name for a custom low-level
|
|
|
|
merge driver. See gitlink:gitattributes[5] for details.
|
|
|
|
|
|
|
|
merge.<driver>.driver::
|
|
|
|
Defines the command that implements a custom low-level
|
|
|
|
merge driver. See gitlink:gitattributes[5] for details.
|
|
|
|
|
|
|
|
merge.<driver>.recursive::
|
|
|
|
Names a low-level merge driver to be used when
|
|
|
|
performing an internal merge between common ancestors.
|
|
|
|
See gitlink:gitattributes[5] for details.
|
|
|
|
|
2006-07-23 07:50:30 +02:00
|
|
|
pack.window::
|
|
|
|
The size of the window used by gitlink:git-pack-objects[1] when no
|
|
|
|
window size is given on the command line. Defaults to 10.
|
|
|
|
|
2007-05-08 15:28:26 +02:00
|
|
|
pack.depth::
|
|
|
|
The maximum delta depth used by gitlink:git-pack-objects[1] when no
|
2007-05-08 15:28:26 +02:00
|
|
|
maximum depth is given on the command line. Defaults to 50.
|
2007-05-08 15:28:26 +02:00
|
|
|
|
2007-07-12 14:55:52 +02:00
|
|
|
pack.windowMemory::
|
|
|
|
The window memory size limit used by gitlink:git-pack-objects[1]
|
|
|
|
when no limit is given on the command line. The value can be
|
|
|
|
suffixed with "k", "m", or "g". Defaults to 0, meaning no
|
|
|
|
limit.
|
|
|
|
|
Custom compression levels for objects and packs
Add config variables pack.compression and core.loosecompression ,
and switch --compression=level to pack-objects.
Loose objects will be compressed using core.loosecompression if set,
else core.compression if set, else Z_BEST_SPEED.
Packed objects will be compressed using --compression=level if seen,
else pack.compression if set, else core.compression if set,
else Z_DEFAULT_COMPRESSION. This is the "pack compression level".
Loose objects added to a pack undeltified will be recompressed
to the pack compression level if it is unequal to the current
loose compression level by the preceding rules, or if the loose
object was written while core.legacyheaders = true. Newly
deltified loose objects are always compressed to the current
pack compression level.
Previously packed objects added to a pack are recompressed
to the current pack compression level exactly when their
deltification status changes, since the previous pack data
cannot be reused.
In either case, the --no-reuse-object switch from the first
patch below will always force recompression to the current pack
compression level, instead of assuming the pack compression level
hasn't changed and pack data can be reused when possible.
This applies on top of the following patches from Nicolas Pitre:
[PATCH] allow for undeltified objects not to be reused
[PATCH] make "repack -f" imply "pack-objects --no-reuse-object"
Signed-off-by: Dana L. How <danahow@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-05-09 22:56:50 +02:00
|
|
|
pack.compression::
|
|
|
|
An integer -1..9, indicating the compression level for objects
|
|
|
|
in a pack file. -1 is the zlib default. 0 means no
|
|
|
|
compression, and 1..9 are various speed/size tradeoffs, 9 being
|
|
|
|
slowest. If not set, defaults to core.compression. If that is
|
2007-11-19 17:58:51 +01:00
|
|
|
not set, defaults to -1, the zlib default, which is "a default
|
|
|
|
compromise between speed and compression (currently equivalent
|
|
|
|
to level 6)."
|
Custom compression levels for objects and packs
Add config variables pack.compression and core.loosecompression ,
and switch --compression=level to pack-objects.
Loose objects will be compressed using core.loosecompression if set,
else core.compression if set, else Z_BEST_SPEED.
Packed objects will be compressed using --compression=level if seen,
else pack.compression if set, else core.compression if set,
else Z_DEFAULT_COMPRESSION. This is the "pack compression level".
Loose objects added to a pack undeltified will be recompressed
to the pack compression level if it is unequal to the current
loose compression level by the preceding rules, or if the loose
object was written while core.legacyheaders = true. Newly
deltified loose objects are always compressed to the current
pack compression level.
Previously packed objects added to a pack are recompressed
to the current pack compression level exactly when their
deltification status changes, since the previous pack data
cannot be reused.
In either case, the --no-reuse-object switch from the first
patch below will always force recompression to the current pack
compression level, instead of assuming the pack compression level
hasn't changed and pack data can be reused when possible.
This applies on top of the following patches from Nicolas Pitre:
[PATCH] allow for undeltified objects not to be reused
[PATCH] make "repack -f" imply "pack-objects --no-reuse-object"
Signed-off-by: Dana L. How <danahow@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-05-09 22:56:50 +02:00
|
|
|
|
2007-05-28 23:20:58 +02:00
|
|
|
pack.deltaCacheSize::
|
2007-08-24 02:44:13 +02:00
|
|
|
The maximum memory in bytes used for caching deltas in
|
2007-05-28 23:20:58 +02:00
|
|
|
gitlink:git-pack-objects[1].
|
|
|
|
A value of 0 means no limit. Defaults to 0.
|
|
|
|
|
2007-05-28 23:20:59 +02:00
|
|
|
pack.deltaCacheLimit::
|
2007-09-10 17:51:34 +02:00
|
|
|
The maximum size of a delta, that is cached in
|
2007-05-28 23:20:59 +02:00
|
|
|
gitlink:git-pack-objects[1]. Defaults to 1000.
|
|
|
|
|
2007-09-10 17:51:34 +02:00
|
|
|
pack.threads::
|
|
|
|
Specifies the number of threads to spawn when searching for best
|
|
|
|
delta matches. This requires that gitlink:git-pack-objects[1]
|
|
|
|
be compiled with pthreads otherwise this option is ignored with a
|
|
|
|
warning. This is meant to reduce packing time on multiprocessor
|
|
|
|
machines. The required amount of memory for the delta search window
|
|
|
|
is however multiplied by the number of threads.
|
|
|
|
|
2007-11-02 04:26:04 +01:00
|
|
|
pack.indexVersion::
|
|
|
|
Specify the default pack index version. Valid values are 1 for
|
|
|
|
legacy pack index used by Git versions prior to 1.5.2, and 2 for
|
|
|
|
the new pack index with capabilities for packs larger than 4 GB
|
|
|
|
as well as proper protection against the repacking of corrupted
|
|
|
|
packs. Version 2 is selected and this config option ignored
|
|
|
|
whenever the corresponding pack is larger than 2 GB. Otherwise
|
|
|
|
the default is 1.
|
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
pull.octopus::
|
|
|
|
The default merge strategy to use when pulling multiple branches
|
|
|
|
at once.
|
|
|
|
|
|
|
|
pull.twohead::
|
|
|
|
The default merge strategy to use when pulling a single branch.
|
|
|
|
|
2006-10-23 18:42:14 +02:00
|
|
|
remote.<name>.url::
|
|
|
|
The URL of a remote repository. See gitlink:git-fetch[1] or
|
|
|
|
gitlink:git-push[1].
|
|
|
|
|
2007-12-03 22:48:54 +01:00
|
|
|
remote.<name>.proxy::
|
|
|
|
For remotes that require curl (http, https and ftp), the URL to
|
|
|
|
the proxy to use for that remote. Set to the empty string to
|
|
|
|
disable proxying for that remote.
|
|
|
|
|
2006-10-23 18:42:14 +02:00
|
|
|
remote.<name>.fetch::
|
|
|
|
The default set of "refspec" for gitlink:git-fetch[1]. See
|
|
|
|
gitlink:git-fetch[1].
|
|
|
|
|
|
|
|
remote.<name>.push::
|
|
|
|
The default set of "refspec" for gitlink:git-push[1]. See
|
|
|
|
gitlink:git-push[1].
|
|
|
|
|
2007-02-20 21:13:43 +01:00
|
|
|
remote.<name>.skipDefaultUpdate::
|
|
|
|
If true, this remote will be skipped by default when updating
|
|
|
|
using the remote subcommand of gitlink:git-remote[1].
|
|
|
|
|
2007-01-19 13:46:16 +01:00
|
|
|
remote.<name>.receivepack::
|
2007-01-25 05:45:39 +01:00
|
|
|
The default program to execute on the remote side when pushing. See
|
2007-01-19 13:46:16 +01:00
|
|
|
option \--exec of gitlink:git-push[1].
|
|
|
|
|
2007-01-25 05:45:39 +01:00
|
|
|
remote.<name>.uploadpack::
|
|
|
|
The default program to execute on the remote side when fetching. See
|
|
|
|
option \--exec of gitlink:git-fetch-pack[1].
|
|
|
|
|
2007-02-24 16:32:56 +01:00
|
|
|
remote.<name>.tagopt::
|
|
|
|
Setting this value to --no-tags disables automatic tag following when fetching
|
|
|
|
from remote <name>
|
|
|
|
|
2007-02-20 21:13:43 +01:00
|
|
|
remotes.<group>::
|
|
|
|
The list of remotes which are fetched by "git remote update
|
|
|
|
<group>". See gitlink:git-remote[1].
|
|
|
|
|
2006-10-14 06:28:58 +02:00
|
|
|
repack.usedeltabaseoffset::
|
|
|
|
Allow gitlink:git-repack[1] to create packs that uses
|
|
|
|
delta-base offset. Defaults to false.
|
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
show.difftree::
|
|
|
|
The default gitlink:git-diff-tree[1] arguments to be used
|
|
|
|
for gitlink:git-show[1].
|
|
|
|
|
|
|
|
showbranch.default::
|
|
|
|
The default set of branches for gitlink:git-show-branch[1].
|
|
|
|
See gitlink:git-show-branch[1].
|
|
|
|
|
2006-07-20 11:30:44 +02:00
|
|
|
tar.umask::
|
2007-08-21 20:01:16 +02:00
|
|
|
This variable can be used to restrict the permission bits of
|
|
|
|
tar archive entries. The default is 0002, which turns off the
|
|
|
|
world write bit. The special value "user" indicates that the
|
|
|
|
archiving user's umask will be used instead. See umask(2) and
|
|
|
|
gitlink:git-archive[1].
|
2006-07-20 11:30:44 +02:00
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
user.email::
|
|
|
|
Your email address to be recorded in any newly created commits.
|
2007-04-29 03:40:28 +02:00
|
|
|
Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
|
|
|
|
'EMAIL' environment variables. See gitlink:git-commit-tree[1].
|
2006-04-25 00:59:33 +02:00
|
|
|
|
|
|
|
user.name::
|
|
|
|
Your full name to be recorded in any newly created commits.
|
2006-06-03 22:27:26 +02:00
|
|
|
Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
|
2006-04-25 00:59:33 +02:00
|
|
|
environment variables. See gitlink:git-commit-tree[1].
|
|
|
|
|
2007-01-26 15:13:46 +01:00
|
|
|
user.signingkey::
|
|
|
|
If gitlink:git-tag[1] is not selecting the key you want it to
|
|
|
|
automatically when creating a signed tag, you can override the
|
|
|
|
default selection with this variable. This option is passed
|
|
|
|
unchanged to gpg's --local-user parameter, so you may specify a key
|
|
|
|
using any method that gpg supports.
|
|
|
|
|
2006-04-25 00:59:33 +02:00
|
|
|
whatchanged.difftree::
|
|
|
|
The default gitlink:git-diff-tree[1] arguments to be used
|
|
|
|
for gitlink:git-whatchanged[1].
|
|
|
|
|
|
|
|
imap::
|
|
|
|
The configuration variables in the 'imap' section are described
|
|
|
|
in gitlink:git-imap-send[1].
|
2006-09-21 02:10:30 +02:00
|
|
|
|
2006-11-01 23:06:21 +01:00
|
|
|
receive.unpackLimit::
|
|
|
|
If the number of objects received in a push is below this
|
|
|
|
limit then the objects will be unpacked into loose object
|
|
|
|
files. However if the number of received objects equals or
|
|
|
|
exceeds this limit then the received pack will be stored as
|
|
|
|
a pack, after adding any missing delta bases. Storing the
|
|
|
|
pack from a push can make the push operation complete faster,
|
|
|
|
especially on slow filesystems.
|
|
|
|
|
|
|
|
receive.denyNonFastForwards::
|
2006-09-21 02:10:30 +02:00
|
|
|
If set to true, git-receive-pack will deny a ref update which is
|
|
|
|
not a fast forward. Use this to prevent such an update via a push,
|
|
|
|
even if that push is forced. This configuration variable is
|
|
|
|
set when initializing a shared repository.
|
|
|
|
|
2007-01-25 02:02:15 +01:00
|
|
|
transfer.unpackLimit::
|
|
|
|
When `fetch.unpackLimit` or `receive.unpackLimit` are
|
|
|
|
not set, the value of this variable is used instead.
|