Documentation / config.txton commit gitweb: allow action specialization in page header (c7d94cd)
   1CONFIGURATION FILE
   2------------------
   3
   4The git configuration file contains a number of variables that affect
   5the git command's behavior. The `.git/config` file in each repository
   6is used to store the configuration for that repository, and
   7`$HOME/.gitconfig` is used to store a per-user configuration as
   8fallback values for the `.git/config` file. The file `/etc/gitconfig`
   9can be used to store a system-wide default configuration.
  10
  11The configuration variables are used by both the git plumbing
  12and the porcelains. The variables are divided into sections, wherein
  13the fully qualified variable name of the variable itself is the last
  14dot-separated segment and the section name is everything before the last
  15dot. The variable names are case-insensitive and only alphanumeric
  16characters are allowed. Some variables may appear multiple times.
  17
  18Syntax
  19~~~~~~
  20
  21The syntax is fairly flexible and permissive; whitespaces are mostly
  22ignored.  The '#' and ';' characters begin comments to the end of line,
  23blank lines are ignored.
  24
  25The file consists of sections and variables.  A section begins with
  26the name of the section in square brackets and continues until the next
  27section begins.  Section names are not case sensitive.  Only alphanumeric
  28characters, `-` and `.` are allowed in section names.  Each variable
  29must belong to some section, which means that there must be a section
  30header before the first setting of a variable.
  31
  32Sections can be further divided into subsections.  To begin a subsection
  33put its name in double quotes, separated by space from the section name,
  34in the section header, like in the example below:
  35
  36--------
  37        [section "subsection"]
  38
  39--------
  40
  41Subsection names are case sensitive and can contain any characters except
  42newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`,
  43respectively).  Section headers cannot span multiple
  44lines.  Variables may belong directly to a section or to a given subsection.
  45You can have `[section]` if you have `[section "subsection"]`, but you
  46don't need to.
  47
  48There is also a case insensitive alternative `[section.subsection]` syntax.
  49In this syntax, subsection names follow the same restrictions as for section
  50names.
  51
  52All the other lines (and the remainder of the line after the section
  53header) are recognized as setting variables, in the form
  54'name = value'.  If there is no equal sign on the line, the entire line
  55is taken as 'name' and the variable is recognized as boolean "true".
  56The variable names are case-insensitive and only alphanumeric
  57characters and `-` are allowed.  There can be more than one value
  58for a given variable; we say then that variable is multivalued.
  59
  60Leading and trailing whitespace in a variable value is discarded.
  61Internal whitespace within a variable value is retained verbatim.
  62
  63The values following the equals sign in variable assign are all either
  64a string, an integer, or a boolean.  Boolean values may be given as yes/no,
  650/1, true/false or on/off.  Case is not significant in boolean values, when
  66converting value to the canonical form using '--bool' type specifier;
  67'git config' will ensure that the output is "true" or "false".
  68
  69String values may be entirely or partially enclosed in double quotes.
  70You need to enclose variable values in double quotes if you want to
  71preserve leading or trailing whitespace, or if the variable value contains
  72comment characters (i.e. it contains '#' or ';').
  73Double quote `"` and backslash `\` characters in variable values must
  74be escaped: use `\"` for `"` and `\\` for `\`.
  75
  76The following escape sequences (beside `\"` and `\\`) are recognized:
  77`\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB)
  78and `\b` for backspace (BS).  No other char escape sequence, nor octal
  79char sequences are valid.
  80
  81Variable values ending in a `\` are continued on the next line in the
  82customary UNIX fashion.
  83
  84Some variables may require a special value format.
  85
  86Example
  87~~~~~~~
  88
  89        # Core variables
  90        [core]
  91                ; Don't trust file modes
  92                filemode = false
  93
  94        # Our diff algorithm
  95        [diff]
  96                external = /usr/local/bin/diff-wrapper
  97                renames = true
  98
  99        [branch "devel"]
 100                remote = origin
 101                merge = refs/heads/devel
 102
 103        # Proxy settings
 104        [core]
 105                gitProxy="ssh" for "kernel.org"
 106                gitProxy=default-proxy ; for the rest
 107
 108Variables
 109~~~~~~~~~
 110
 111Note that this list is non-comprehensive and not necessarily complete.
 112For command-specific variables, you will find a more detailed description
 113in the appropriate manual page. You will find a description of non-core
 114porcelain configuration variables in the respective porcelain documentation.
 115
 116advice.*::
 117        When set to 'true', display the given optional help message.
 118        When set to 'false', do not display. The configuration variables
 119        are:
 120+
 121--
 122        pushNonFastForward::
 123                Advice shown when linkgit:git-push[1] refuses
 124                non-fast-forward refs. Default: true.
 125        statusHints::
 126                Directions on how to stage/unstage/add shown in the
 127                output of linkgit:git-status[1] and the template shown
 128                when writing commit messages. Default: true.
 129        commitBeforeMerge::
 130                Advice shown when linkgit:git-merge[1] refuses to
 131                merge to avoid overwriting local changes.
 132                Default: true.
 133        resolveConflict::
 134                Advices shown by various commands when conflicts
 135                prevent the operation from being performed.
 136                Default: true.
 137        implicitIdentity::
 138                Advice on how to set your identity configuration when
 139                your information is guessed from the system username and
 140                domain name. Default: true.
 141
 142        detachedHead::
 143                Advice shown when you used linkgit::git-checkout[1] to
 144                move to the detach HEAD state, to instruct how to create
 145                a local branch after the fact.  Default: true.
 146--
 147
 148core.fileMode::
 149        If false, the executable bit differences between the index and
 150        the working copy are ignored; useful on broken filesystems like FAT.
 151        See linkgit:git-update-index[1].
 152+
 153The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
 154will probe and set core.fileMode false if appropriate when the
 155repository is created.
 156
 157core.ignoreCygwinFSTricks::
 158        This option is only used by Cygwin implementation of Git. If false,
 159        the Cygwin stat() and lstat() functions are used. This may be useful
 160        if your repository consists of a few separate directories joined in
 161        one hierarchy using Cygwin mount. If true, Git uses native Win32 API
 162        whenever it is possible and falls back to Cygwin functions only to
 163        handle symbol links. The native mode is more than twice faster than
 164        normal Cygwin l/stat() functions. True by default, unless core.filemode
 165        is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's
 166        POSIX emulation is required to support core.filemode.
 167
 168core.ignorecase::
 169        If true, this option enables various workarounds to enable
 170        git to work better on filesystems that are not case sensitive,
 171        like FAT. For example, if a directory listing finds
 172        "makefile" when git expects "Makefile", git will assume
 173        it is really the same file, and continue to remember it as
 174        "Makefile".
 175+
 176The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]
 177will probe and set core.ignorecase true if appropriate when the repository
 178is created.
 179
 180core.trustctime::
 181        If false, the ctime differences between the index and the
 182        working copy are ignored; useful when the inode change time
 183        is regularly modified by something outside Git (file system
 184        crawlers and some backup systems).
 185        See linkgit:git-update-index[1]. True by default.
 186
 187core.quotepath::
 188        The commands that output paths (e.g. 'ls-files',
 189        'diff'), when not given the `-z` option, will quote
 190        "unusual" characters in the pathname by enclosing the
 191        pathname in a double-quote pair and with backslashes the
 192        same way strings in C source code are quoted.  If this
 193        variable is set to false, the bytes higher than 0x80 are
 194        not quoted but output as verbatim.  Note that double
 195        quote, backslash and control characters are always
 196        quoted without `-z` regardless of the setting of this
 197        variable.
 198
 199core.eol::
 200        Sets the line ending type to use in the working directory for
 201        files that have the `text` property set.  Alternatives are
 202        'lf', 'crlf' and 'native', which uses the platform's native
 203        line ending.  The default value is `native`.  See
 204        linkgit:gitattributes[5] for more information on end-of-line
 205        conversion.
 206
 207core.safecrlf::
 208        If true, makes git check if converting `CRLF` is reversible when
 209        end-of-line conversion is active.  Git will verify if a command
 210        modifies a file in the work tree either directly or indirectly.
 211        For example, committing a file followed by checking out the
 212        same file should yield the original file in the work tree.  If
 213        this is not the case for the current setting of
 214        `core.autocrlf`, git will reject the file.  The variable can
 215        be set to "warn", in which case git will only warn about an
 216        irreversible conversion but continue the operation.
 217+
 218CRLF conversion bears a slight chance of corrupting data.
 219When it is enabled, git will convert CRLF to LF during commit and LF to
 220CRLF during checkout.  A file that contains a mixture of LF and
 221CRLF before the commit cannot be recreated by git.  For text
 222files this is the right thing to do: it corrects line endings
 223such that we have only LF line endings in the repository.
 224But for binary files that are accidentally classified as text the
 225conversion can corrupt data.
 226+
 227If you recognize such corruption early you can easily fix it by
 228setting the conversion type explicitly in .gitattributes.  Right
 229after committing you still have the original file in your work
 230tree and this file is not yet corrupted.  You can explicitly tell
 231git that this file is binary and git will handle the file
 232appropriately.
 233+
 234Unfortunately, the desired effect of cleaning up text files with
 235mixed line endings and the undesired effect of corrupting binary
 236files cannot be distinguished.  In both cases CRLFs are removed
 237in an irreversible way.  For text files this is the right thing
 238to do because CRLFs are line endings, while for binary files
 239converting CRLFs corrupts data.
 240+
 241Note, this safety check does not mean that a checkout will generate a
 242file identical to the original file for a different setting of
 243`core.eol` and `core.autocrlf`, but only for the current one.  For
 244example, a text file with `LF` would be accepted with `core.eol=lf`
 245and could later be checked out with `core.eol=crlf`, in which case the
 246resulting file would contain `CRLF`, although the original file
 247contained `LF`.  However, in both work trees the line endings would be
 248consistent, that is either all `LF` or all `CRLF`, but never mixed.  A
 249file with mixed line endings would be reported by the `core.safecrlf`
 250mechanism.
 251
 252core.autocrlf::
 253        Setting this variable to "true" is almost the same as setting
 254        the `text` attribute to "auto" on all files except that text
 255        files are not guaranteed to be normalized: files that contain
 256        `CRLF` in the repository will not be touched.  Use this
 257        setting if you want to have `CRLF` line endings in your
 258        working directory even though the repository does not have
 259        normalized line endings.  This variable can be set to 'input',
 260        in which case no output conversion is performed.
 261
 262core.symlinks::
 263        If false, symbolic links are checked out as small plain files that
 264        contain the link text. linkgit:git-update-index[1] and
 265        linkgit:git-add[1] will not change the recorded type to regular
 266        file. Useful on filesystems like FAT that do not support
 267        symbolic links.
 268+
 269The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
 270will probe and set core.symlinks false if appropriate when the repository
 271is created.
 272
 273core.gitProxy::
 274        A "proxy command" to execute (as 'command host port') instead
 275        of establishing direct connection to the remote server when
 276        using the git protocol for fetching. If the variable value is
 277        in the "COMMAND for DOMAIN" format, the command is applied only
 278        on hostnames ending with the specified domain string. This variable
 279        may be set multiple times and is matched in the given order;
 280        the first match wins.
 281+
 282Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
 283(which always applies universally, without the special "for"
 284handling).
 285+
 286The special string `none` can be used as the proxy command to
 287specify that no proxy be used for a given domain pattern.
 288This is useful for excluding servers inside a firewall from
 289proxy use, while defaulting to a common proxy for external domains.
 290
 291core.ignoreStat::
 292        If true, commands which modify both the working tree and the index
 293        will mark the updated paths with the "assume unchanged" bit in the
 294        index. These marked files are then assumed to stay unchanged in the
 295        working copy, until you mark them otherwise manually - Git will not
 296        detect the file changes by lstat() calls. This is useful on systems
 297        where those are very slow, such as Microsoft Windows.
 298        See linkgit:git-update-index[1].
 299        False by default.
 300
 301core.preferSymlinkRefs::
 302        Instead of the default "symref" format for HEAD
 303        and other symbolic reference files, use symbolic links.
 304        This is sometimes needed to work with old scripts that
 305        expect HEAD to be a symbolic link.
 306
 307core.bare::
 308        If true this repository is assumed to be 'bare' and has no
 309        working directory associated with it.  If this is the case a
 310        number of commands that require a working directory will be
 311        disabled, such as linkgit:git-add[1] or linkgit:git-merge[1].
 312+
 313This setting is automatically guessed by linkgit:git-clone[1] or
 314linkgit:git-init[1] when the repository was created.  By default a
 315repository that ends in "/.git" is assumed to be not bare (bare =
 316false), while all other repositories are assumed to be bare (bare
 317= true).
 318
 319core.worktree::
 320        Set the path to the root of the work tree.
 321        This can be overridden by the GIT_WORK_TREE environment
 322        variable and the '--work-tree' command line option. It can be
 323        an absolute path or a relative path to the .git directory,
 324        either specified by --git-dir or GIT_DIR, or automatically
 325        discovered.
 326        If --git-dir or GIT_DIR are specified but none of
 327        --work-tree, GIT_WORK_TREE and core.worktree is specified,
 328        the current working directory is regarded as the root of the
 329        work tree.
 330+
 331Note that this variable is honored even when set in a configuration
 332file in a ".git" subdirectory of a directory, and its value differs
 333from the latter directory (e.g. "/path/to/.git/config" has
 334core.worktree set to "/different/path"), which is most likely a
 335misconfiguration.  Running git commands in "/path/to" directory will
 336still use "/different/path" as the root of the work tree and can cause
 337great confusion to the users.
 338
 339core.logAllRefUpdates::
 340        Enable the reflog. Updates to a ref <ref> is logged to the file
 341        "$GIT_DIR/logs/<ref>", by appending the new and old
 342        SHA1, the date/time and the reason of the update, but
 343        only when the file exists.  If this configuration
 344        variable is set to true, missing "$GIT_DIR/logs/<ref>"
 345        file is automatically created for branch heads.
 346+
 347This information can be used to determine what commit
 348was the tip of a branch "2 days ago".
 349+
 350This value is true by default in a repository that has
 351a working directory associated with it, and false by
 352default in a bare repository.
 353
 354core.repositoryFormatVersion::
 355        Internal variable identifying the repository format and layout
 356        version.
 357
 358core.sharedRepository::
 359        When 'group' (or 'true'), the repository is made shareable between
 360        several users in a group (making sure all the files and objects are
 361        group-writable). When 'all' (or 'world' or 'everybody'), the
 362        repository will be readable by all users, additionally to being
 363        group-shareable. When 'umask' (or 'false'), git will use permissions
 364        reported by umask(2). When '0xxx', where '0xxx' is an octal number,
 365        files in the repository will have this mode value. '0xxx' will override
 366        user's umask value (whereas the other options will only override
 367        requested parts of the user's umask value). Examples: '0660' will make
 368        the repo read/write-able for the owner and group, but inaccessible to
 369        others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a
 370        repository that is group-readable but not group-writable.
 371        See linkgit:git-init[1]. False by default.
 372
 373core.warnAmbiguousRefs::
 374        If true, git will warn you if the ref name you passed it is ambiguous
 375        and might match multiple refs in the .git/refs/ tree. True by default.
 376
 377core.compression::
 378        An integer -1..9, indicating a default compression level.
 379        -1 is the zlib default. 0 means no compression,
 380        and 1..9 are various speed/size tradeoffs, 9 being slowest.
 381        If set, this provides a default to other compression variables,
 382        such as 'core.loosecompression' and 'pack.compression'.
 383
 384core.loosecompression::
 385        An integer -1..9, indicating the compression level for objects that
 386        are not in a pack file. -1 is the zlib default. 0 means no
 387        compression, and 1..9 are various speed/size tradeoffs, 9 being
 388        slowest.  If not set,  defaults to core.compression.  If that is
 389        not set,  defaults to 1 (best speed).
 390
 391core.packedGitWindowSize::
 392        Number of bytes of a pack file to map into memory in a
 393        single mapping operation.  Larger window sizes may allow
 394        your system to process a smaller number of large pack files
 395        more quickly.  Smaller window sizes will negatively affect
 396        performance due to increased calls to the operating system's
 397        memory manager, but may improve performance when accessing
 398        a large number of large pack files.
 399+
 400Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
 401MiB on 32 bit platforms and 1 GiB on 64 bit platforms.  This should
 402be reasonable for all users/operating systems.  You probably do
 403not need to adjust this value.
 404+
 405Common unit suffixes of 'k', 'm', or 'g' are supported.
 406
 407core.packedGitLimit::
 408        Maximum number of bytes to map simultaneously into memory
 409        from pack files.  If Git needs to access more than this many
 410        bytes at once to complete an operation it will unmap existing
 411        regions to reclaim virtual address space within the process.
 412+
 413Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
 414This should be reasonable for all users/operating systems, except on
 415the largest projects.  You probably do not need to adjust this value.
 416+
 417Common unit suffixes of 'k', 'm', or 'g' are supported.
 418
 419core.deltaBaseCacheLimit::
 420        Maximum number of bytes to reserve for caching base objects
 421        that may be referenced by multiple deltified objects.  By storing the
 422        entire decompressed base objects in a cache Git is able
 423        to avoid unpacking and decompressing frequently used base
 424        objects multiple times.
 425+
 426Default is 16 MiB on all platforms.  This should be reasonable
 427for all users/operating systems, except on the largest projects.
 428You probably do not need to adjust this value.
 429+
 430Common unit suffixes of 'k', 'm', or 'g' are supported.
 431
 432core.bigFileThreshold::
 433        Files larger than this size are stored deflated, without
 434        attempting delta compression.  Storing large files without
 435        delta compression avoids excessive memory usage, at the
 436        slight expense of increased disk usage.
 437+
 438Default is 512 MiB on all platforms.  This should be reasonable
 439for most projects as source code and other text files can still
 440be delta compressed, but larger binary media files won't be.
 441+
 442Common unit suffixes of 'k', 'm', or 'g' are supported.
 443+
 444Currently only linkgit:git-fast-import[1] honors this setting.
 445
 446core.excludesfile::
 447        In addition to '.gitignore' (per-directory) and
 448        '.git/info/exclude', git looks into this file for patterns
 449        of files which are not meant to be tracked.  "{tilde}/" is expanded
 450        to the value of `$HOME` and "{tilde}user/" to the specified user's
 451        home directory.  See linkgit:gitignore[5].
 452
 453core.askpass::
 454        Some commands (e.g. svn and http interfaces) that interactively
 455        ask for a password can be told to use an external program given
 456        via the value of this variable. Can be overridden by the 'GIT_ASKPASS'
 457        environment variable. If not set, fall back to the value of the
 458        'SSH_ASKPASS' environment variable or, failing that, a simple password
 459        prompt. The external program shall be given a suitable prompt as
 460        command line argument and write the password on its STDOUT.
 461
 462core.attributesfile::
 463        In addition to '.gitattributes' (per-directory) and
 464        '.git/info/attributes', git looks into this file for attributes
 465        (see linkgit:gitattributes[5]). Path expansions are made the same
 466        way as for `core.excludesfile`.
 467
 468core.editor::
 469        Commands such as `commit` and `tag` that lets you edit
 470        messages by launching an editor uses the value of this
 471        variable when it is set, and the environment variable
 472        `GIT_EDITOR` is not set.  See linkgit:git-var[1].
 473
 474core.pager::
 475        The command that git will use to paginate output.  Can
 476        be overridden with the `GIT_PAGER` environment
 477        variable.  Note that git sets the `LESS` environment
 478        variable to `FRSX` if it is unset when it runs the
 479        pager.  One can change these settings by setting the
 480        `LESS` variable to some other value.  Alternately,
 481        these settings can be overridden on a project or
 482        global basis by setting the `core.pager` option.
 483        Setting `core.pager` has no affect on the `LESS`
 484        environment variable behaviour above, so if you want
 485        to override git's default settings this way, you need
 486        to be explicit.  For example, to disable the S option
 487        in a backward compatible manner, set `core.pager`
 488        to `less -+$LESS -FRX`.  This will be passed to the
 489        shell by git, which will translate the final command to
 490        `LESS=FRSX less -+FRSX -FRX`.
 491
 492core.whitespace::
 493        A comma separated list of common whitespace problems to
 494        notice.  'git diff' will use `color.diff.whitespace` to
 495        highlight them, and 'git apply --whitespace=error' will
 496        consider them as errors.  You can prefix `-` to disable
 497        any of them (e.g. `-trailing-space`):
 498+
 499* `blank-at-eol` treats trailing whitespaces at the end of the line
 500  as an error (enabled by default).
 501* `space-before-tab` treats a space character that appears immediately
 502  before a tab character in the initial indent part of the line as an
 503  error (enabled by default).
 504* `indent-with-non-tab` treats a line that is indented with 8 or more
 505  space characters as an error (not enabled by default).
 506* `tab-in-indent` treats a tab character in the initial indent part of
 507  the line as an error (not enabled by default).
 508* `blank-at-eof` treats blank lines added at the end of file as an error
 509  (enabled by default).
 510* `trailing-space` is a short-hand to cover both `blank-at-eol` and
 511  `blank-at-eof`.
 512* `cr-at-eol` treats a carriage-return at the end of line as
 513  part of the line terminator, i.e. with it, `trailing-space`
 514  does not trigger if the character before such a carriage-return
 515  is not a whitespace (not enabled by default).
 516
 517core.fsyncobjectfiles::
 518        This boolean will enable 'fsync()' when writing object files.
 519+
 520This is a total waste of time and effort on a filesystem that orders
 521data writes properly, but can be useful for filesystems that do not use
 522journalling (traditional UNIX filesystems) or that only journal metadata
 523and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback").
 524
 525core.preloadindex::
 526        Enable parallel index preload for operations like 'git diff'
 527+
 528This can speed up operations like 'git diff' and 'git status' especially
 529on filesystems like NFS that have weak caching semantics and thus
 530relatively high IO latencies.  With this set to 'true', git will do the
 531index comparison to the filesystem data in parallel, allowing
 532overlapping IO's.
 533
 534core.createObject::
 535        You can set this to 'link', in which case a hardlink followed by
 536        a delete of the source are used to make sure that object creation
 537        will not overwrite existing objects.
 538+
 539On some file system/operating system combinations, this is unreliable.
 540Set this config setting to 'rename' there; However, This will remove the
 541check that makes sure that existing object files will not get overwritten.
 542
 543core.notesRef::
 544        When showing commit messages, also show notes which are stored in
 545        the given ref.  The ref must be fully qualified.  If the given
 546        ref does not exist, it is not an error but means that no
 547        notes should be printed.
 548+
 549This setting defaults to "refs/notes/commits", and it can be overridden by
 550the 'GIT_NOTES_REF' environment variable.  See linkgit:git-notes[1].
 551
 552core.sparseCheckout::
 553        Enable "sparse checkout" feature. See section "Sparse checkout" in
 554        linkgit:git-read-tree[1] for more information.
 555
 556add.ignore-errors::
 557        Tells 'git add' to continue adding files when some files cannot be
 558        added due to indexing errors. Equivalent to the '--ignore-errors'
 559        option of linkgit:git-add[1].
 560
 561alias.*::
 562        Command aliases for the linkgit:git[1] command wrapper - e.g.
 563        after defining "alias.last = cat-file commit HEAD", the invocation
 564        "git last" is equivalent to "git cat-file commit HEAD". To avoid
 565        confusion and troubles with script usage, aliases that
 566        hide existing git commands are ignored. Arguments are split by
 567        spaces, the usual shell quoting and escaping is supported.
 568        quote pair and a backslash can be used to quote them.
 569+
 570If the alias expansion is prefixed with an exclamation point,
 571it will be treated as a shell command.  For example, defining
 572"alias.new = !gitk --all --not ORIG_HEAD", the invocation
 573"git new" is equivalent to running the shell command
 574"gitk --all --not ORIG_HEAD".  Note that shell commands will be
 575executed from the top-level directory of a repository, which may
 576not necessarily be the current directory.
 577
 578am.keepcr::
 579        If true, git-am will call git-mailsplit for patches in mbox format
 580        with parameter '--keep-cr'. In this case git-mailsplit will
 581        not remove `\r` from lines ending with `\r\n`. Can be overridden
 582        by giving '--no-keep-cr' from the command line.
 583        See linkgit:git-am[1], linkgit:git-mailsplit[1].
 584
 585apply.ignorewhitespace::
 586        When set to 'change', tells 'git apply' to ignore changes in
 587        whitespace, in the same way as the '--ignore-space-change'
 588        option.
 589        When set to one of: no, none, never, false tells 'git apply' to
 590        respect all whitespace differences.
 591        See linkgit:git-apply[1].
 592
 593apply.whitespace::
 594        Tells 'git apply' how to handle whitespaces, in the same way
 595        as the '--whitespace' option. See linkgit:git-apply[1].
 596
 597branch.autosetupmerge::
 598        Tells 'git branch' and 'git checkout' to set up new branches
 599        so that linkgit:git-pull[1] will appropriately merge from the
 600        starting point branch. Note that even if this option is not set,
 601        this behavior can be chosen per-branch using the `--track`
 602        and `--no-track` options. The valid settings are: `false` -- no
 603        automatic setup is done; `true` -- automatic setup is done when the
 604        starting point is a remote branch; `always` -- automatic setup is
 605        done when the starting point is either a local branch or remote
 606        branch. This option defaults to true.
 607
 608branch.autosetuprebase::
 609        When a new branch is created with 'git branch' or 'git checkout'
 610        that tracks another branch, this variable tells git to set
 611        up pull to rebase instead of merge (see "branch.<name>.rebase").
 612        When `never`, rebase is never automatically set to true.
 613        When `local`, rebase is set to true for tracked branches of
 614        other local branches.
 615        When `remote`, rebase is set to true for tracked branches of
 616        remote branches.
 617        When `always`, rebase will be set to true for all tracking
 618        branches.
 619        See "branch.autosetupmerge" for details on how to set up a
 620        branch to track another branch.
 621        This option defaults to never.
 622
 623branch.<name>.remote::
 624        When in branch <name>, it tells 'git fetch' and 'git push' which
 625        remote to fetch from/push to.  It defaults to `origin` if no remote is
 626        configured. `origin` is also used if you are not on any branch.
 627
 628branch.<name>.merge::
 629        Defines, together with branch.<name>.remote, the upstream branch
 630        for the given branch. It tells 'git fetch'/'git pull' which
 631        branch to merge and can also affect 'git push' (see push.default).
 632        When in branch <name>, it tells 'git fetch' the default
 633        refspec to be marked for merging in FETCH_HEAD. The value is
 634        handled like the remote part of a refspec, and must match a
 635        ref which is fetched from the remote given by
 636        "branch.<name>.remote".
 637        The merge information is used by 'git pull' (which at first calls
 638        'git fetch') to lookup the default branch for merging. Without
 639        this option, 'git pull' defaults to merge the first refspec fetched.
 640        Specify multiple values to get an octopus merge.
 641        If you wish to setup 'git pull' so that it merges into <name> from
 642        another branch in the local repository, you can point
 643        branch.<name>.merge to the desired branch, and use the special setting
 644        `.` (a period) for branch.<name>.remote.
 645
 646branch.<name>.mergeoptions::
 647        Sets default options for merging into branch <name>. The syntax and
 648        supported options are the same as those of linkgit:git-merge[1], but
 649        option values containing whitespace characters are currently not
 650        supported.
 651
 652branch.<name>.rebase::
 653        When true, rebase the branch <name> on top of the fetched branch,
 654        instead of merging the default branch from the default remote when
 655        "git pull" is run.
 656        *NOTE*: this is a possibly dangerous operation; do *not* use
 657        it unless you understand the implications (see linkgit:git-rebase[1]
 658        for details).
 659
 660browser.<tool>.cmd::
 661        Specify the command to invoke the specified browser. The
 662        specified command is evaluated in shell with the URLs passed
 663        as arguments. (See linkgit:git-web--browse[1].)
 664
 665browser.<tool>.path::
 666        Override the path for the given tool that may be used to
 667        browse HTML help (see '-w' option in linkgit:git-help[1]) or a
 668        working repository in gitweb (see linkgit:git-instaweb[1]).
 669
 670clean.requireForce::
 671        A boolean to make git-clean do nothing unless given -f
 672        or -n.   Defaults to true.
 673
 674color.branch::
 675        A boolean to enable/disable color in the output of
 676        linkgit:git-branch[1]. May be set to `always`,
 677        `false` (or `never`) or `auto` (or `true`), in which case colors are used
 678        only when the output is to a terminal. Defaults to false.
 679
 680color.branch.<slot>::
 681        Use customized color for branch coloration. `<slot>` is one of
 682        `current` (the current branch), `local` (a local branch),
 683        `remote` (a tracking branch in refs/remotes/), `plain` (other
 684        refs).
 685+
 686The value for these configuration variables is a list of colors (at most
 687two) and attributes (at most one), separated by spaces.  The colors
 688accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
 689`magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
 690`blink` and `reverse`.  The first color given is the foreground; the
 691second is the background.  The position of the attribute, if any,
 692doesn't matter.
 693
 694color.diff::
 695        When set to `always`, always use colors in patch.
 696        When false (or `never`), never.  When set to `true` or `auto`, use
 697        colors only when the output is to the terminal. Defaults to false.
 698
 699color.diff.<slot>::
 700        Use customized color for diff colorization.  `<slot>` specifies
 701        which part of the patch to use the specified color, and is one
 702        of `plain` (context text), `meta` (metainformation), `frag`
 703        (hunk header), 'func' (function in hunk header), `old` (removed lines),
 704        `new` (added lines), `commit` (commit headers), or `whitespace`
 705        (highlighting whitespace errors). The values of these variables may be
 706        specified as in color.branch.<slot>.
 707
 708color.decorate.<slot>::
 709        Use customized color for 'git log --decorate' output.  `<slot>` is one
 710        of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local
 711        branches, remote tracking branches, tags, stash and HEAD, respectively.
 712
 713color.grep::
 714        When set to `always`, always highlight matches.  When `false` (or
 715        `never`), never.  When set to `true` or `auto`, use color only
 716        when the output is written to the terminal.  Defaults to `false`.
 717
 718color.grep.<slot>::
 719        Use customized color for grep colorization.  `<slot>` specifies which
 720        part of the line to use the specified color, and is one of
 721+
 722--
 723`context`;;
 724        non-matching text in context lines (when using `-A`, `-B`, or `-C`)
 725`filename`;;
 726        filename prefix (when not using `-h`)
 727`function`;;
 728        function name lines (when using `-p`)
 729`linenumber`;;
 730        line number prefix (when using `-n`)
 731`match`;;
 732        matching text
 733`selected`;;
 734        non-matching text in selected lines
 735`separator`;;
 736        separators between fields on a line (`:`, `-`, and `=`)
 737        and between hunks (`--`)
 738--
 739+
 740The values of these variables may be specified as in color.branch.<slot>.
 741
 742color.interactive::
 743        When set to `always`, always use colors for interactive prompts
 744        and displays (such as those used by "git-add --interactive").
 745        When false (or `never`), never.  When set to `true` or `auto`, use
 746        colors only when the output is to the terminal. Defaults to false.
 747
 748color.interactive.<slot>::
 749        Use customized color for 'git add --interactive'
 750        output. `<slot>` may be `prompt`, `header`, `help` or `error`, for
 751        four distinct types of normal output from interactive
 752        commands.  The values of these variables may be specified as
 753        in color.branch.<slot>.
 754
 755color.pager::
 756        A boolean to enable/disable colored output when the pager is in
 757        use (default is true).
 758
 759color.showbranch::
 760        A boolean to enable/disable color in the output of
 761        linkgit:git-show-branch[1]. May be set to `always`,
 762        `false` (or `never`) or `auto` (or `true`), in which case colors are used
 763        only when the output is to a terminal. Defaults to false.
 764
 765color.status::
 766        A boolean to enable/disable color in the output of
 767        linkgit:git-status[1]. May be set to `always`,
 768        `false` (or `never`) or `auto` (or `true`), in which case colors are used
 769        only when the output is to a terminal. Defaults to false.
 770
 771color.status.<slot>::
 772        Use customized color for status colorization. `<slot>` is
 773        one of `header` (the header text of the status message),
 774        `added` or `updated` (files which are added but not committed),
 775        `changed` (files which are changed but not added in the index),
 776        `untracked` (files which are not tracked by git), or
 777        `nobranch` (the color the 'no branch' warning is shown in, defaulting
 778        to red). The values of these variables may be specified as in
 779        color.branch.<slot>.
 780
 781color.ui::
 782        When set to `always`, always use colors in all git commands which
 783        are capable of colored output. When false (or `never`), never. When
 784        set to `true` or `auto`, use colors only when the output is to the
 785        terminal. When more specific variables of color.* are set, they always
 786        take precedence over this setting. Defaults to false.
 787
 788commit.status::
 789        A boolean to enable/disable inclusion of status information in the
 790        commit message template when using an editor to prepare the commit
 791        message.  Defaults to true.
 792
 793commit.template::
 794        Specify a file to use as the template for new commit messages.
 795        "{tilde}/" is expanded to the value of `$HOME` and "{tilde}user/" to the
 796        specified user's home directory.
 797
 798diff.autorefreshindex::
 799        When using 'git diff' to compare with work tree
 800        files, do not consider stat-only change as changed.
 801        Instead, silently run `git update-index --refresh` to
 802        update the cached stat information for paths whose
 803        contents in the work tree match the contents in the
 804        index.  This option defaults to true.  Note that this
 805        affects only 'git diff' Porcelain, and not lower level
 806        'diff' commands such as 'git diff-files'.
 807
 808diff.external::
 809        If this config variable is set, diff generation is not
 810        performed using the internal diff machinery, but using the
 811        given command.  Can be overridden with the `GIT_EXTERNAL_DIFF'
 812        environment variable.  The command is called with parameters
 813        as described under "git Diffs" in linkgit:git[1].  Note: if
 814        you want to use an external diff program only on a subset of
 815        your files, you might want to use linkgit:gitattributes[5] instead.
 816
 817diff.mnemonicprefix::
 818        If set, 'git diff' uses a prefix pair that is different from the
 819        standard "a/" and "b/" depending on what is being compared.  When
 820        this configuration is in effect, reverse diff output also swaps
 821        the order of the prefixes:
 822`git diff`;;
 823        compares the (i)ndex and the (w)ork tree;
 824`git diff HEAD`;;
 825         compares a (c)ommit and the (w)ork tree;
 826`git diff --cached`;;
 827        compares a (c)ommit and the (i)ndex;
 828`git diff HEAD:file1 file2`;;
 829        compares an (o)bject and a (w)ork tree entity;
 830`git diff --no-index a b`;;
 831        compares two non-git things (1) and (2).
 832
 833diff.noprefix::
 834        If set, 'git diff' does not show any source or destination prefix.
 835
 836diff.renameLimit::
 837        The number of files to consider when performing the copy/rename
 838        detection; equivalent to the 'git diff' option '-l'.
 839
 840diff.renames::
 841        Tells git to detect renames.  If set to any boolean value, it
 842        will enable basic rename detection.  If set to "copies" or
 843        "copy", it will detect copies, as well.
 844
 845diff.ignoreSubmodules::
 846        Sets the default value of --ignore-submodules. Note that this
 847        affects only 'git diff' Porcelain, and not lower level 'diff'
 848        commands such as 'git diff-files'. 'git checkout' also honors
 849        this setting when reporting uncommitted changes.
 850
 851diff.suppressBlankEmpty::
 852        A boolean to inhibit the standard behavior of printing a space
 853        before each empty output line. Defaults to false.
 854
 855diff.tool::
 856        Controls which diff tool is used.  `diff.tool` overrides
 857        `merge.tool` when used by linkgit:git-difftool[1] and has
 858        the same valid values as `merge.tool` minus "tortoisemerge"
 859        and plus "kompare".
 860
 861difftool.<tool>.path::
 862        Override the path for the given tool.  This is useful in case
 863        your tool is not in the PATH.
 864
 865difftool.<tool>.cmd::
 866        Specify the command to invoke the specified diff tool.
 867        The specified command is evaluated in shell with the following
 868        variables available:  'LOCAL' is set to the name of the temporary
 869        file containing the contents of the diff pre-image and 'REMOTE'
 870        is set to the name of the temporary file containing the contents
 871        of the diff post-image.
 872
 873difftool.prompt::
 874        Prompt before each invocation of the diff tool.
 875
 876diff.wordRegex::
 877        A POSIX Extended Regular Expression used to determine what is a "word"
 878        when performing word-by-word difference calculations.  Character
 879        sequences that match the regular expression are "words", all other
 880        characters are *ignorable* whitespace.
 881
 882fetch.unpackLimit::
 883        If the number of objects fetched over the git native
 884        transfer is below this
 885        limit, then the objects will be unpacked into loose object
 886        files. However if the number of received objects equals or
 887        exceeds this limit then the received pack will be stored as
 888        a pack, after adding any missing delta bases.  Storing the
 889        pack from a push can make the push operation complete faster,
 890        especially on slow filesystems.  If not set, the value of
 891        `transfer.unpackLimit` is used instead.
 892
 893format.attach::
 894        Enable multipart/mixed attachments as the default for
 895        'format-patch'.  The value can also be a double quoted string
 896        which will enable attachments as the default and set the
 897        value as the boundary.  See the --attach option in
 898        linkgit:git-format-patch[1].
 899
 900format.numbered::
 901        A boolean which can enable or disable sequence numbers in patch
 902        subjects.  It defaults to "auto" which enables it only if there
 903        is more than one patch.  It can be enabled or disabled for all
 904        messages by setting it to "true" or "false".  See --numbered
 905        option in linkgit:git-format-patch[1].
 906
 907format.headers::
 908        Additional email headers to include in a patch to be submitted
 909        by mail.  See linkgit:git-format-patch[1].
 910
 911format.to::
 912format.cc::
 913        Additional recipients to include in a patch to be submitted
 914        by mail.  See the --to and --cc options in
 915        linkgit:git-format-patch[1].
 916
 917format.subjectprefix::
 918        The default for format-patch is to output files with the '[PATCH]'
 919        subject prefix. Use this variable to change that prefix.
 920
 921format.signature::
 922        The default for format-patch is to output a signature containing
 923        the git version number. Use this variable to change that default.
 924        Set this variable to the empty string ("") to suppress
 925        signature generation.
 926
 927format.suffix::
 928        The default for format-patch is to output files with the suffix
 929        `.patch`. Use this variable to change that suffix (make sure to
 930        include the dot if you want it).
 931
 932format.pretty::
 933        The default pretty format for log/show/whatchanged command,
 934        See linkgit:git-log[1], linkgit:git-show[1],
 935        linkgit:git-whatchanged[1].
 936
 937format.thread::
 938        The default threading style for 'git format-patch'.  Can be
 939        a boolean value, or `shallow` or `deep`.  `shallow` threading
 940        makes every mail a reply to the head of the series,
 941        where the head is chosen from the cover letter, the
 942        `\--in-reply-to`, and the first patch mail, in this order.
 943        `deep` threading makes every mail a reply to the previous one.
 944        A true boolean value is the same as `shallow`, and a false
 945        value disables threading.
 946
 947format.signoff::
 948    A boolean value which lets you enable the `-s/--signoff` option of
 949    format-patch by default. *Note:* Adding the Signed-off-by: line to a
 950    patch should be a conscious act and means that you certify you have
 951    the rights to submit this work under the same open source license.
 952    Please see the 'SubmittingPatches' document for further discussion.
 953
 954gc.aggressiveWindow::
 955        The window size parameter used in the delta compression
 956        algorithm used by 'git gc --aggressive'.  This defaults
 957        to 250.
 958
 959gc.auto::
 960        When there are approximately more than this many loose
 961        objects in the repository, `git gc --auto` will pack them.
 962        Some Porcelain commands use this command to perform a
 963        light-weight garbage collection from time to time.  The
 964        default value is 6700.  Setting this to 0 disables it.
 965
 966gc.autopacklimit::
 967        When there are more than this many packs that are not
 968        marked with `*.keep` file in the repository, `git gc
 969        --auto` consolidates them into one larger pack.  The
 970        default value is 50.  Setting this to 0 disables it.
 971
 972gc.packrefs::
 973        Running `git pack-refs` in a repository renders it
 974        unclonable by Git versions prior to 1.5.1.2 over dumb
 975        transports such as HTTP.  This variable determines whether
 976        'git gc' runs `git pack-refs`. This can be set to `nobare`
 977        to enable it within all non-bare repos or it can be set to a
 978        boolean value.  The default is `true`.
 979
 980gc.pruneexpire::
 981        When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.
 982        Override the grace period with this config variable.  The value
 983        "now" may be used to disable this  grace period and always prune
 984        unreachable objects immediately.
 985
 986gc.reflogexpire::
 987gc.<pattern>.reflogexpire::
 988        'git reflog expire' removes reflog entries older than
 989        this time; defaults to 90 days.  With "<pattern>" (e.g.
 990        "refs/stash") in the middle the setting applies only to
 991        the refs that match the <pattern>.
 992
 993gc.reflogexpireunreachable::
 994gc.<ref>.reflogexpireunreachable::
 995        'git reflog expire' removes reflog entries older than
 996        this time and are not reachable from the current tip;
 997        defaults to 30 days.  With "<pattern>" (e.g. "refs/stash")
 998        in the middle, the setting applies only to the refs that
 999        match the <pattern>.
1000
1001gc.rerereresolved::
1002        Records of conflicted merge you resolved earlier are
1003        kept for this many days when 'git rerere gc' is run.
1004        The default is 60 days.  See linkgit:git-rerere[1].
1005
1006gc.rerereunresolved::
1007        Records of conflicted merge you have not resolved are
1008        kept for this many days when 'git rerere gc' is run.
1009        The default is 15 days.  See linkgit:git-rerere[1].
1010
1011gitcvs.commitmsgannotation::
1012        Append this string to each commit message. Set to empty string
1013        to disable this feature. Defaults to "via git-CVS emulator".
1014
1015gitcvs.enabled::
1016        Whether the CVS server interface is enabled for this repository.
1017        See linkgit:git-cvsserver[1].
1018
1019gitcvs.logfile::
1020        Path to a log file where the CVS server interface well... logs
1021        various stuff. See linkgit:git-cvsserver[1].
1022
1023gitcvs.usecrlfattr::
1024        If true, the server will look up the end-of-line conversion
1025        attributes for files to determine the '-k' modes to use. If
1026        the attributes force git to treat a file as text,
1027        the '-k' mode will be left blank so CVS clients will
1028        treat it as text. If they suppress text conversion, the file
1029        will be set with '-kb' mode, which suppresses any newline munging
1030        the client might otherwise do. If the attributes do not allow
1031        the file type to be determined, then 'gitcvs.allbinary' is
1032        used. See linkgit:gitattributes[5].
1033
1034gitcvs.allbinary::
1035        This is used if 'gitcvs.usecrlfattr' does not resolve
1036        the correct '-kb' mode to use. If true, all
1037        unresolved files are sent to the client in
1038        mode '-kb'. This causes the client to treat them
1039        as binary files, which suppresses any newline munging it
1040        otherwise might do. Alternatively, if it is set to "guess",
1041        then the contents of the file are examined to decide if
1042        it is binary, similar to 'core.autocrlf'.
1043
1044gitcvs.dbname::
1045        Database used by git-cvsserver to cache revision information
1046        derived from the git repository. The exact meaning depends on the
1047        used database driver, for SQLite (which is the default driver) this
1048        is a filename. Supports variable substitution (see
1049        linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).
1050        Default: '%Ggitcvs.%m.sqlite'
1051
1052gitcvs.dbdriver::
1053        Used Perl DBI driver. You can specify any available driver
1054        for this here, but it might not work. git-cvsserver is tested
1055        with 'DBD::SQLite', reported to work with 'DBD::Pg', and
1056        reported *not* to work with 'DBD::mysql'. Experimental feature.
1057        May not contain double colons (`:`). Default: 'SQLite'.
1058        See linkgit:git-cvsserver[1].
1059
1060gitcvs.dbuser, gitcvs.dbpass::
1061        Database user and password. Only useful if setting 'gitcvs.dbdriver',
1062        since SQLite has no concept of database users and/or passwords.
1063        'gitcvs.dbuser' supports variable substitution (see
1064        linkgit:git-cvsserver[1] for details).
1065
1066gitcvs.dbTableNamePrefix::
1067        Database table name prefix.  Prepended to the names of any
1068        database tables used, allowing a single database to be used
1069        for several repositories.  Supports variable substitution (see
1070        linkgit:git-cvsserver[1] for details).  Any non-alphabetic
1071        characters will be replaced with underscores.
1072
1073All gitcvs variables except for 'gitcvs.usecrlfattr' and
1074'gitcvs.allbinary' can also be specified as
1075'gitcvs.<access_method>.<varname>' (where 'access_method'
1076is one of "ext" and "pserver") to make them apply only for the given
1077access method.
1078
1079gui.commitmsgwidth::
1080        Defines how wide the commit message window is in the
1081        linkgit:git-gui[1]. "75" is the default.
1082
1083gui.diffcontext::
1084        Specifies how many context lines should be used in calls to diff
1085        made by the linkgit:git-gui[1]. The default is "5".
1086
1087gui.encoding::
1088        Specifies the default encoding to use for displaying of
1089        file contents in linkgit:git-gui[1] and linkgit:gitk[1].
1090        It can be overridden by setting the 'encoding' attribute
1091        for relevant files (see linkgit:gitattributes[5]).
1092        If this option is not set, the tools default to the
1093        locale encoding.
1094
1095gui.matchtrackingbranch::
1096        Determines if new branches created with linkgit:git-gui[1] should
1097        default to tracking remote branches with matching names or
1098        not. Default: "false".
1099
1100gui.newbranchtemplate::
1101        Is used as suggested name when creating new branches using the
1102        linkgit:git-gui[1].
1103
1104gui.pruneduringfetch::
1105        "true" if linkgit:git-gui[1] should prune tracking branches when
1106        performing a fetch. The default value is "false".
1107
1108gui.trustmtime::
1109        Determines if linkgit:git-gui[1] should trust the file modification
1110        timestamp or not. By default the timestamps are not trusted.
1111
1112gui.spellingdictionary::
1113        Specifies the dictionary used for spell checking commit messages in
1114        the linkgit:git-gui[1]. When set to "none" spell checking is turned
1115        off.
1116
1117gui.fastcopyblame::
1118        If true, 'git gui blame' uses `-C` instead of `-C -C` for original
1119        location detection. It makes blame significantly faster on huge
1120        repositories at the expense of less thorough copy detection.
1121
1122gui.copyblamethreshold::
1123        Specifies the threshold to use in 'git gui blame' original location
1124        detection, measured in alphanumeric characters. See the
1125        linkgit:git-blame[1] manual for more information on copy detection.
1126
1127gui.blamehistoryctx::
1128        Specifies the radius of history context in days to show in
1129        linkgit:gitk[1] for the selected commit, when the `Show History
1130        Context` menu item is invoked from 'git gui blame'. If this
1131        variable is set to zero, the whole history is shown.
1132
1133guitool.<name>.cmd::
1134        Specifies the shell command line to execute when the corresponding item
1135        of the linkgit:git-gui[1] `Tools` menu is invoked. This option is
1136        mandatory for every tool. The command is executed from the root of
1137        the working directory, and in the environment it receives the name of
1138        the tool as 'GIT_GUITOOL', the name of the currently selected file as
1139        'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if
1140        the head is detached, 'CUR_BRANCH' is empty).
1141
1142guitool.<name>.needsfile::
1143        Run the tool only if a diff is selected in the GUI. It guarantees
1144        that 'FILENAME' is not empty.
1145
1146guitool.<name>.noconsole::
1147        Run the command silently, without creating a window to display its
1148        output.
1149
1150guitool.<name>.norescan::
1151        Don't rescan the working directory for changes after the tool
1152        finishes execution.
1153
1154guitool.<name>.confirm::
1155        Show a confirmation dialog before actually running the tool.
1156
1157guitool.<name>.argprompt::
1158        Request a string argument from the user, and pass it to the tool
1159        through the 'ARGS' environment variable. Since requesting an
1160        argument implies confirmation, the 'confirm' option has no effect
1161        if this is enabled. If the option is set to 'true', 'yes', or '1',
1162        the dialog uses a built-in generic prompt; otherwise the exact
1163        value of the variable is used.
1164
1165guitool.<name>.revprompt::
1166        Request a single valid revision from the user, and set the
1167        'REVISION' environment variable. In other aspects this option
1168        is similar to 'argprompt', and can be used together with it.
1169
1170guitool.<name>.revunmerged::
1171        Show only unmerged branches in the 'revprompt' subdialog.
1172        This is useful for tools similar to merge or rebase, but not
1173        for things like checkout or reset.
1174
1175guitool.<name>.title::
1176        Specifies the title to use for the prompt dialog. The default
1177        is the tool name.
1178
1179guitool.<name>.prompt::
1180        Specifies the general prompt string to display at the top of
1181        the dialog, before subsections for 'argprompt' and 'revprompt'.
1182        The default value includes the actual command.
1183
1184help.browser::
1185        Specify the browser that will be used to display help in the
1186        'web' format. See linkgit:git-help[1].
1187
1188help.format::
1189        Override the default help format used by linkgit:git-help[1].
1190        Values 'man', 'info', 'web' and 'html' are supported. 'man' is
1191        the default. 'web' and 'html' are the same.
1192
1193help.autocorrect::
1194        Automatically correct and execute mistyped commands after
1195        waiting for the given number of deciseconds (0.1 sec). If more
1196        than one command can be deduced from the entered text, nothing
1197        will be executed.  If the value of this option is negative,
1198        the corrected command will be executed immediately. If the
1199        value is 0 - the command will be just shown but not executed.
1200        This is the default.
1201
1202http.proxy::
1203        Override the HTTP proxy, normally configured using the 'http_proxy'
1204        environment variable (see linkgit:curl[1]).  This can be overridden
1205        on a per-remote basis; see remote.<name>.proxy
1206
1207http.sslVerify::
1208        Whether to verify the SSL certificate when fetching or pushing
1209        over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
1210        variable.
1211
1212http.sslCert::
1213        File containing the SSL certificate when fetching or pushing
1214        over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
1215        variable.
1216
1217http.sslKey::
1218        File containing the SSL private key when fetching or pushing
1219        over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
1220        variable.
1221
1222http.sslCertPasswordProtected::
1223        Enable git's password prompt for the SSL certificate.  Otherwise
1224        OpenSSL will prompt the user, possibly many times, if the
1225        certificate or private key is encrypted.  Can be overridden by the
1226        'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.
1227
1228http.sslCAInfo::
1229        File containing the certificates to verify the peer with when
1230        fetching or pushing over HTTPS. Can be overridden by the
1231        'GIT_SSL_CAINFO' environment variable.
1232
1233http.sslCAPath::
1234        Path containing files with the CA certificates to verify the peer
1235        with when fetching or pushing over HTTPS. Can be overridden
1236        by the 'GIT_SSL_CAPATH' environment variable.
1237
1238http.maxRequests::
1239        How many HTTP requests to launch in parallel. Can be overridden
1240        by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
1241
1242http.minSessions::
1243        The number of curl sessions (counted across slots) to be kept across
1244        requests. They will not be ended with curl_easy_cleanup() until
1245        http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
1246        value will be capped at 1. Defaults to 1.
1247
1248http.postBuffer::
1249        Maximum size in bytes of the buffer used by smart HTTP
1250        transports when POSTing data to the remote system.
1251        For requests larger than this buffer size, HTTP/1.1 and
1252        Transfer-Encoding: chunked is used to avoid creating a
1253        massive pack file locally.  Default is 1 MiB, which is
1254        sufficient for most requests.
1255
1256http.lowSpeedLimit, http.lowSpeedTime::
1257        If the HTTP transfer speed is less than 'http.lowSpeedLimit'
1258        for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
1259        Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
1260        'GIT_HTTP_LOW_SPEED_TIME' environment variables.
1261
1262http.noEPSV::
1263        A boolean which disables using of EPSV ftp command by curl.
1264        This can helpful with some "poor" ftp servers which don't
1265        support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
1266        environment variable. Default is false (curl will use EPSV).
1267
1268http.useragent::
1269        The HTTP USER_AGENT string presented to an HTTP server.  The default
1270        value represents the version of the client git such as git/1.7.1.
1271        This option allows you to override this value to a more common value
1272        such as Mozilla/4.0.  This may be necessary, for instance, if
1273        connecting through a firewall that restricts HTTP connections to a set
1274        of common USER_AGENT strings (but not including those like git/1.7.1).
1275        Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.
1276
1277i18n.commitEncoding::
1278        Character encoding the commit messages are stored in; git itself
1279        does not care per se, but this information is necessary e.g. when
1280        importing commits from emails or in the gitk graphical history
1281        browser (and possibly at other places in the future or in other
1282        porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.
1283
1284i18n.logOutputEncoding::
1285        Character encoding the commit messages are converted to when
1286        running 'git log' and friends.
1287
1288imap::
1289        The configuration variables in the 'imap' section are described
1290        in linkgit:git-imap-send[1].
1291
1292init.templatedir::
1293        Specify the directory from which templates will be copied.
1294        (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)
1295
1296instaweb.browser::
1297        Specify the program that will be used to browse your working
1298        repository in gitweb. See linkgit:git-instaweb[1].
1299
1300instaweb.httpd::
1301        The HTTP daemon command-line to start gitweb on your working
1302        repository. See linkgit:git-instaweb[1].
1303
1304instaweb.local::
1305        If true the web server started by linkgit:git-instaweb[1] will
1306        be bound to the local IP (127.0.0.1).
1307
1308instaweb.modulepath::
1309        The default module path for linkgit:git-instaweb[1] to use
1310        instead of /usr/lib/apache2/modules.  Only used if httpd
1311        is Apache.
1312
1313instaweb.port::
1314        The port number to bind the gitweb httpd to. See
1315        linkgit:git-instaweb[1].
1316
1317interactive.singlekey::
1318        In interactive commands, allow the user to provide one-letter
1319        input with a single key (i.e., without hitting enter).
1320        Currently this is used only by the `\--patch` mode of
1321        linkgit:git-add[1].  Note that this setting is silently
1322        ignored if portable keystroke input is not available.
1323
1324log.date::
1325        Set the default date-time mode for the 'log' command.
1326        Setting a value for log.date is similar to using 'git log''s
1327        `\--date` option.  Possible values are `relative`, `local`,
1328        `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]
1329        for details.
1330
1331log.decorate::
1332        Print out the ref names of any commits that are shown by the log
1333        command. If 'short' is specified, the ref name prefixes 'refs/heads/',
1334        'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is
1335        specified, the full ref name (including prefix) will be printed.
1336        This is the same as the log commands '--decorate' option.
1337
1338log.showroot::
1339        If true, the initial commit will be shown as a big creation event.
1340        This is equivalent to a diff against an empty tree.
1341        Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which
1342        normally hide the root commit will now show it. True by default.
1343
1344mailmap.file::
1345        The location of an augmenting mailmap file. The default
1346        mailmap, located in the root of the repository, is loaded
1347        first, then the mailmap file pointed to by this variable.
1348        The location of the mailmap file may be in a repository
1349        subdirectory, or somewhere outside of the repository itself.
1350        See linkgit:git-shortlog[1] and linkgit:git-blame[1].
1351
1352man.viewer::
1353        Specify the programs that may be used to display help in the
1354        'man' format. See linkgit:git-help[1].
1355
1356man.<tool>.cmd::
1357        Specify the command to invoke the specified man viewer. The
1358        specified command is evaluated in shell with the man page
1359        passed as argument. (See linkgit:git-help[1].)
1360
1361man.<tool>.path::
1362        Override the path for the given tool that may be used to
1363        display help in the 'man' format. See linkgit:git-help[1].
1364
1365include::merge-config.txt[]
1366
1367mergetool.<tool>.path::
1368        Override the path for the given tool.  This is useful in case
1369        your tool is not in the PATH.
1370
1371mergetool.<tool>.cmd::
1372        Specify the command to invoke the specified merge tool.  The
1373        specified command is evaluated in shell with the following
1374        variables available: 'BASE' is the name of a temporary file
1375        containing the common base of the files to be merged, if available;
1376        'LOCAL' is the name of a temporary file containing the contents of
1377        the file on the current branch; 'REMOTE' is the name of a temporary
1378        file containing the contents of the file from the branch being
1379        merged; 'MERGED' contains the name of the file to which the merge
1380        tool should write the results of a successful merge.
1381
1382mergetool.<tool>.trustExitCode::
1383        For a custom merge command, specify whether the exit code of
1384        the merge command can be used to determine whether the merge was
1385        successful.  If this is not set to true then the merge target file
1386        timestamp is checked and the merge assumed to have been successful
1387        if the file has been updated, otherwise the user is prompted to
1388        indicate the success of the merge.
1389
1390mergetool.keepBackup::
1391        After performing a merge, the original file with conflict markers
1392        can be saved as a file with a `.orig` extension.  If this variable
1393        is set to `false` then this file is not preserved.  Defaults to
1394        `true` (i.e. keep the backup files).
1395
1396mergetool.keepTemporaries::
1397        When invoking a custom merge tool, git uses a set of temporary
1398        files to pass to the tool. If the tool returns an error and this
1399        variable is set to `true`, then these temporary files will be
1400        preserved, otherwise they will be removed after the tool has
1401        exited. Defaults to `false`.
1402
1403mergetool.prompt::
1404        Prompt before each invocation of the merge resolution program.
1405
1406notes.displayRef::
1407        The (fully qualified) refname from which to show notes when
1408        showing commit messages.  The value of this variable can be set
1409        to a glob, in which case notes from all matching refs will be
1410        shown.  You may also specify this configuration variable
1411        several times.  A warning will be issued for refs that do not
1412        exist, but a glob that does not match any refs is silently
1413        ignored.
1414+
1415This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`
1416environment variable, which must be a colon separated list of refs or
1417globs.
1418+
1419The effective value of "core.notesRef" (possibly overridden by
1420GIT_NOTES_REF) is also implicitly added to the list of refs to be
1421displayed.
1422
1423notes.rewrite.<command>::
1424        When rewriting commits with <command> (currently `amend` or
1425        `rebase`) and this variable is set to `true`, git
1426        automatically copies your notes from the original to the
1427        rewritten commit.  Defaults to `true`, but see
1428        "notes.rewriteRef" below.
1429
1430notes.rewriteMode::
1431        When copying notes during a rewrite (see the
1432        "notes.rewrite.<command>" option), determines what to do if
1433        the target commit already has a note.  Must be one of
1434        `overwrite`, `concatenate`, or `ignore`.  Defaults to
1435        `concatenate`.
1436+
1437This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`
1438environment variable.
1439
1440notes.rewriteRef::
1441        When copying notes during a rewrite, specifies the (fully
1442        qualified) ref whose notes should be copied.  The ref may be a
1443        glob, in which case notes in all matching refs will be copied.
1444        You may also specify this configuration several times.
1445+
1446Does not have a default value; you must configure this variable to
1447enable note rewriting.
1448+
1449This setting can be overridden with the `GIT_NOTES_REWRITE_REF`
1450environment variable, which must be a colon separated list of refs or
1451globs.
1452
1453pack.window::
1454        The size of the window used by linkgit:git-pack-objects[1] when no
1455        window size is given on the command line. Defaults to 10.
1456
1457pack.depth::
1458        The maximum delta depth used by linkgit:git-pack-objects[1] when no
1459        maximum depth is given on the command line. Defaults to 50.
1460
1461pack.windowMemory::
1462        The window memory size limit used by linkgit:git-pack-objects[1]
1463        when no limit is given on the command line.  The value can be
1464        suffixed with "k", "m", or "g".  Defaults to 0, meaning no
1465        limit.
1466
1467pack.compression::
1468        An integer -1..9, indicating the compression level for objects
1469        in a pack file. -1 is the zlib default. 0 means no
1470        compression, and 1..9 are various speed/size tradeoffs, 9 being
1471        slowest.  If not set,  defaults to core.compression.  If that is
1472        not set,  defaults to -1, the zlib default, which is "a default
1473        compromise between speed and compression (currently equivalent
1474        to level 6)."
1475+
1476Note that changing the compression level will not automatically recompress
1477all existing objects. You can force recompression by passing the -F option
1478to linkgit:git-repack[1].
1479
1480pack.deltaCacheSize::
1481        The maximum memory in bytes used for caching deltas in
1482        linkgit:git-pack-objects[1] before writing them out to a pack.
1483        This cache is used to speed up the writing object phase by not
1484        having to recompute the final delta result once the best match
1485        for all objects is found.  Repacking large repositories on machines
1486        which are tight with memory might be badly impacted by this though,
1487        especially if this cache pushes the system into swapping.
1488        A value of 0 means no limit. The smallest size of 1 byte may be
1489        used to virtually disable this cache. Defaults to 256 MiB.
1490
1491pack.deltaCacheLimit::
1492        The maximum size of a delta, that is cached in
1493        linkgit:git-pack-objects[1]. This cache is used to speed up the
1494        writing object phase by not having to recompute the final delta
1495        result once the best match for all objects is found. Defaults to 1000.
1496
1497pack.threads::
1498        Specifies the number of threads to spawn when searching for best
1499        delta matches.  This requires that linkgit:git-pack-objects[1]
1500        be compiled with pthreads otherwise this option is ignored with a
1501        warning. This is meant to reduce packing time on multiprocessor
1502        machines. The required amount of memory for the delta search window
1503        is however multiplied by the number of threads.
1504        Specifying 0 will cause git to auto-detect the number of CPU's
1505        and set the number of threads accordingly.
1506
1507pack.indexVersion::
1508        Specify the default pack index version.  Valid values are 1 for
1509        legacy pack index used by Git versions prior to 1.5.2, and 2 for
1510        the new pack index with capabilities for packs larger than 4 GB
1511        as well as proper protection against the repacking of corrupted
1512        packs.  Version 2 is the default.  Note that version 2 is enforced
1513        and this config option ignored whenever the corresponding pack is
1514        larger than 2 GB.
1515+
1516If you have an old git that does not understand the version 2 `{asterisk}.idx` file,
1517cloning or fetching over a non native protocol (e.g. "http" and "rsync")
1518that will copy both `{asterisk}.pack` file and corresponding `{asterisk}.idx` file from the
1519other side may give you a repository that cannot be accessed with your
1520older version of git. If the `{asterisk}.pack` file is smaller than 2 GB, however,
1521you can use linkgit:git-index-pack[1] on the *.pack file to regenerate
1522the `{asterisk}.idx` file.
1523
1524pack.packSizeLimit::
1525        The maximum size of a pack.  This setting only affects
1526        packing to a file when repacking, i.e. the git:// protocol
1527        is unaffected.  It can be overridden by the `\--max-pack-size`
1528        option of linkgit:git-repack[1]. The minimum size allowed is
1529        limited to 1 MiB. The default is unlimited.
1530        Common unit suffixes of 'k', 'm', or 'g' are
1531        supported.
1532
1533pager.<cmd>::
1534        Allows turning on or off pagination of the output of a
1535        particular git subcommand when writing to a tty.  If
1536        `\--paginate` or `\--no-pager` is specified on the command line,
1537        it takes precedence over this option.  To disable pagination for
1538        all commands, set `core.pager` or `GIT_PAGER` to `cat`.
1539
1540pretty.<name>::
1541        Alias for a --pretty= format string, as specified in
1542        linkgit:git-log[1]. Any aliases defined here can be used just
1543        as the built-in pretty formats could. For example,
1544        running `git config pretty.changelog "format:{asterisk} %H %s"`
1545        would cause the invocation `git log --pretty=changelog`
1546        to be equivalent to running `git log "--pretty=format:{asterisk} %H %s"`.
1547        Note that an alias with the same name as a built-in format
1548        will be silently ignored.
1549
1550pull.octopus::
1551        The default merge strategy to use when pulling multiple branches
1552        at once.
1553
1554pull.twohead::
1555        The default merge strategy to use when pulling a single branch.
1556
1557push.default::
1558        Defines the action git push should take if no refspec is given
1559        on the command line, no refspec is configured in the remote, and
1560        no refspec is implied by any of the options given on the command
1561        line. Possible values are:
1562+
1563* `nothing` - do not push anything.
1564* `matching` - push all matching branches.
1565  All branches having the same name in both ends are considered to be
1566  matching. This is the default.
1567* `tracking` - push the current branch to its upstream branch.
1568* `current` - push the current branch to a branch of the same name.
1569
1570rebase.stat::
1571        Whether to show a diffstat of what changed upstream since the last
1572        rebase. False by default.
1573
1574rebase.autosquash::
1575        If set to true enable '--autosquash' option by default.
1576
1577receive.autogc::
1578        By default, git-receive-pack will run "git-gc --auto" after
1579        receiving data from git-push and updating refs.  You can stop
1580        it by setting this variable to false.
1581
1582receive.fsckObjects::
1583        If it is set to true, git-receive-pack will check all received
1584        objects. It will abort in the case of a malformed object or a
1585        broken link. The result of an abort are only dangling objects.
1586        Defaults to false.
1587
1588receive.unpackLimit::
1589        If the number of objects received in a push is below this
1590        limit then the objects will be unpacked into loose object
1591        files. However if the number of received objects equals or
1592        exceeds this limit then the received pack will be stored as
1593        a pack, after adding any missing delta bases.  Storing the
1594        pack from a push can make the push operation complete faster,
1595        especially on slow filesystems.  If not set, the value of
1596        `transfer.unpackLimit` is used instead.
1597
1598receive.denyDeletes::
1599        If set to true, git-receive-pack will deny a ref update that deletes
1600        the ref. Use this to prevent such a ref deletion via a push.
1601
1602receive.denyDeleteCurrent::
1603        If set to true, git-receive-pack will deny a ref update that
1604        deletes the currently checked out branch of a non-bare repository.
1605
1606receive.denyCurrentBranch::
1607        If set to true or "refuse", git-receive-pack will deny a ref update
1608        to the currently checked out branch of a non-bare repository.
1609        Such a push is potentially dangerous because it brings the HEAD
1610        out of sync with the index and working tree. If set to "warn",
1611        print a warning of such a push to stderr, but allow the push to
1612        proceed. If set to false or "ignore", allow such pushes with no
1613        message. Defaults to "refuse".
1614
1615receive.denyNonFastForwards::
1616        If set to true, git-receive-pack will deny a ref update which is
1617        not a fast-forward. Use this to prevent such an update via a push,
1618        even if that push is forced. This configuration variable is
1619        set when initializing a shared repository.
1620
1621receive.updateserverinfo::
1622        If set to true, git-receive-pack will run git-update-server-info
1623        after receiving data from git-push and updating refs.
1624
1625remote.<name>.url::
1626        The URL of a remote repository.  See linkgit:git-fetch[1] or
1627        linkgit:git-push[1].
1628
1629remote.<name>.pushurl::
1630        The push URL of a remote repository.  See linkgit:git-push[1].
1631
1632remote.<name>.proxy::
1633        For remotes that require curl (http, https and ftp), the URL to
1634        the proxy to use for that remote.  Set to the empty string to
1635        disable proxying for that remote.
1636
1637remote.<name>.fetch::
1638        The default set of "refspec" for linkgit:git-fetch[1]. See
1639        linkgit:git-fetch[1].
1640
1641remote.<name>.push::
1642        The default set of "refspec" for linkgit:git-push[1]. See
1643        linkgit:git-push[1].
1644
1645remote.<name>.mirror::
1646        If true, pushing to this remote will automatically behave
1647        as if the `\--mirror` option was given on the command line.
1648
1649remote.<name>.skipDefaultUpdate::
1650        If true, this remote will be skipped by default when updating
1651        using linkgit:git-fetch[1] or the `update` subcommand of
1652        linkgit:git-remote[1].
1653
1654remote.<name>.skipFetchAll::
1655        If true, this remote will be skipped by default when updating
1656        using linkgit:git-fetch[1] or the `update` subcommand of
1657        linkgit:git-remote[1].
1658
1659remote.<name>.receivepack::
1660        The default program to execute on the remote side when pushing.  See
1661        option \--receive-pack of linkgit:git-push[1].
1662
1663remote.<name>.uploadpack::
1664        The default program to execute on the remote side when fetching.  See
1665        option \--upload-pack of linkgit:git-fetch-pack[1].
1666
1667remote.<name>.tagopt::
1668        Setting this value to \--no-tags disables automatic tag following when
1669        fetching from remote <name>. Setting it to \--tags will fetch every
1670        tag from remote <name>, even if they are not reachable from remote
1671        branch heads. Passing these flags directly to linkgit:git-fetch[1] can
1672        override this setting. See options \--tags and \--no-tags of
1673        linkgit:git-fetch[1].
1674
1675remote.<name>.vcs::
1676        Setting this to a value <vcs> will cause git to interact with
1677        the remote with the git-remote-<vcs> helper.
1678
1679remotes.<group>::
1680        The list of remotes which are fetched by "git remote update
1681        <group>".  See linkgit:git-remote[1].
1682
1683repack.usedeltabaseoffset::
1684        By default, linkgit:git-repack[1] creates packs that use
1685        delta-base offset. If you need to share your repository with
1686        git older than version 1.4.4, either directly or via a dumb
1687        protocol such as http, then you need to set this option to
1688        "false" and repack. Access from old git versions over the
1689        native protocol are unaffected by this option.
1690
1691rerere.autoupdate::
1692        When set to true, `git-rerere` updates the index with the
1693        resulting contents after it cleanly resolves conflicts using
1694        previously recorded resolution.  Defaults to false.
1695
1696rerere.enabled::
1697        Activate recording of resolved conflicts, so that identical
1698        conflict hunks can be resolved automatically, should they
1699        be encountered again.  linkgit:git-rerere[1] command is by
1700        default enabled if you create `rr-cache` directory under
1701        `$GIT_DIR`, but can be disabled by setting this option to false.
1702
1703sendemail.identity::
1704        A configuration identity. When given, causes values in the
1705        'sendemail.<identity>' subsection to take precedence over
1706        values in the 'sendemail' section. The default identity is
1707        the value of 'sendemail.identity'.
1708
1709sendemail.smtpencryption::
1710        See linkgit:git-send-email[1] for description.  Note that this
1711        setting is not subject to the 'identity' mechanism.
1712
1713sendemail.smtpssl::
1714        Deprecated alias for 'sendemail.smtpencryption = ssl'.
1715
1716sendemail.<identity>.*::
1717        Identity-specific versions of the 'sendemail.*' parameters
1718        found below, taking precedence over those when the this
1719        identity is selected, through command-line or
1720        'sendemail.identity'.
1721
1722sendemail.aliasesfile::
1723sendemail.aliasfiletype::
1724sendemail.bcc::
1725sendemail.cc::
1726sendemail.cccmd::
1727sendemail.chainreplyto::
1728sendemail.confirm::
1729sendemail.envelopesender::
1730sendemail.from::
1731sendemail.multiedit::
1732sendemail.signedoffbycc::
1733sendemail.smtppass::
1734sendemail.suppresscc::
1735sendemail.suppressfrom::
1736sendemail.to::
1737sendemail.smtpdomain::
1738sendemail.smtpserver::
1739sendemail.smtpserverport::
1740sendemail.smtpserveroption::
1741sendemail.smtpuser::
1742sendemail.thread::
1743sendemail.validate::
1744        See linkgit:git-send-email[1] for description.
1745
1746sendemail.signedoffcc::
1747        Deprecated alias for 'sendemail.signedoffbycc'.
1748
1749showbranch.default::
1750        The default set of branches for linkgit:git-show-branch[1].
1751        See linkgit:git-show-branch[1].
1752
1753status.relativePaths::
1754        By default, linkgit:git-status[1] shows paths relative to the
1755        current directory. Setting this variable to `false` shows paths
1756        relative to the repository root (this was the default for git
1757        prior to v1.5.4).
1758
1759status.showUntrackedFiles::
1760        By default, linkgit:git-status[1] and linkgit:git-commit[1] show
1761        files which are not currently tracked by Git. Directories which
1762        contain only untracked files, are shown with the directory name
1763        only. Showing untracked files means that Git needs to lstat() all
1764        all the files in the whole repository, which might be slow on some
1765        systems. So, this variable controls how the commands displays
1766        the untracked files. Possible values are:
1767+
1768--
1769* `no` - Show no untracked files.
1770* `normal` - Show untracked files and directories.
1771* `all` - Show also individual files in untracked directories.
1772--
1773+
1774If this variable is not specified, it defaults to 'normal'.
1775This variable can be overridden with the -u|--untracked-files option
1776of linkgit:git-status[1] and linkgit:git-commit[1].
1777
1778status.submodulesummary::
1779        Defaults to false.
1780        If this is set to a non zero number or true (identical to -1 or an
1781        unlimited number), the submodule summary will be enabled and a
1782        summary of commits for modified submodules will be shown (see
1783        --summary-limit option of linkgit:git-submodule[1]).
1784
1785submodule.<name>.path::
1786submodule.<name>.url::
1787submodule.<name>.update::
1788        The path within this project, URL, and the updating strategy
1789        for a submodule.  These variables are initially populated
1790        by 'git submodule init'; edit them to override the
1791        URL and other values found in the `.gitmodules` file.  See
1792        linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.
1793
1794submodule.<name>.ignore::
1795        Defines under what circumstances "git status" and the diff family show
1796        a submodule as modified. When set to "all", it will never be considered
1797        modified, "dirty" will ignore all changes to the submodules work tree and
1798        takes only differences between the HEAD of the submodule and the commit
1799        recorded in the superproject into account. "untracked" will additionally
1800        let submodules with modified tracked files in their work tree show up.
1801        Using "none" (the default when this option is not set) also shows
1802        submodules that have untracked files in their work tree as changed.
1803        This setting overrides any setting made in .gitmodules for this submodule,
1804        both settings can be overridden on the command line by using the
1805        "--ignore-submodules" option.
1806
1807tar.umask::
1808        This variable can be used to restrict the permission bits of
1809        tar archive entries.  The default is 0002, which turns off the
1810        world write bit.  The special value "user" indicates that the
1811        archiving user's umask will be used instead.  See umask(2) and
1812        linkgit:git-archive[1].
1813
1814transfer.unpackLimit::
1815        When `fetch.unpackLimit` or `receive.unpackLimit` are
1816        not set, the value of this variable is used instead.
1817        The default value is 100.
1818
1819url.<base>.insteadOf::
1820        Any URL that starts with this value will be rewritten to
1821        start, instead, with <base>. In cases where some site serves a
1822        large number of repositories, and serves them with multiple
1823        access methods, and some users need to use different access
1824        methods, this feature allows people to specify any of the
1825        equivalent URLs and have git automatically rewrite the URL to
1826        the best alternative for the particular user, even for a
1827        never-before-seen repository on the site.  When more than one
1828        insteadOf strings match a given URL, the longest match is used.
1829
1830url.<base>.pushInsteadOf::
1831        Any URL that starts with this value will not be pushed to;
1832        instead, it will be rewritten to start with <base>, and the
1833        resulting URL will be pushed to. In cases where some site serves
1834        a large number of repositories, and serves them with multiple
1835        access methods, some of which do not allow push, this feature
1836        allows people to specify a pull-only URL and have git
1837        automatically use an appropriate URL to push, even for a
1838        never-before-seen repository on the site.  When more than one
1839        pushInsteadOf strings match a given URL, the longest match is
1840        used.  If a remote has an explicit pushurl, git will ignore this
1841        setting for that remote.
1842
1843user.email::
1844        Your email address to be recorded in any newly created commits.
1845        Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
1846        'EMAIL' environment variables.  See linkgit:git-commit-tree[1].
1847
1848user.name::
1849        Your full name to be recorded in any newly created commits.
1850        Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
1851        environment variables.  See linkgit:git-commit-tree[1].
1852
1853user.signingkey::
1854        If linkgit:git-tag[1] is not selecting the key you want it to
1855        automatically when creating a signed tag, you can override the
1856        default selection with this variable.  This option is passed
1857        unchanged to gpg's --local-user parameter, so you may specify a key
1858        using any method that gpg supports.
1859
1860web.browser::
1861        Specify a web browser that may be used by some commands.
1862        Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]
1863        may use it.