4 The git configuration file contains a number of variables that affect
5 the git command's behavior. `.git/config` file for each repository
6 is used to store the information for that repository, and
7 `$HOME/.gitconfig` is used to store per user information to give
8 fallback values for `.git/config` file. The file `/etc/gitconfig`
9 can be used to store system-wide defaults.
11 They can be used by both the git plumbing
12 and the porcelains. The variables are divided into sections, where
13 in the fully qualified variable name the variable itself is the last
14 dot-separated segment and the section name is everything before the last
15 dot. The variable names are case-insensitive and only alphanumeric
16 characters are allowed. Some variables may appear multiple times.
21 The syntax is fairly flexible and permissive; whitespaces are mostly
22 ignored. The '#' and ';' characters begin comments to the end of line,
23 blank lines are ignored.
25 The file consists of sections and variables. A section begins with
26 the name of the section in square brackets and continues until the next
27 section begins. Section names are not case sensitive. Only alphanumeric
28 characters, '`-`' and '`.`' are allowed in section names. Each variable
29 must belong to some section, which means that there must be section
30 header before first setting of a variable.
32 Sections can be further divided into subsections. To begin a subsection
33 put its name in double quotes, separated by space from the section name,
34 in the section header, like in example below:
37 [section "subsection"]
41 Subsection names can contain any characters except newline (doublequote
42 '`"`' and backslash have to be escaped as '`\"`' and '`\\`',
43 respectively) and are case sensitive. Section header cannot span multiple
44 lines. Variables may belong directly to a section or to a given subsection.
45 You can have `[section]` if you have `[section "subsection"]`, but you
48 There is also (case insensitive) alternative `[section.subsection]` syntax.
49 In this syntax subsection names follow the same restrictions as for section
52 All the other lines are recognized as setting variables, in the form
53 'name = value'. If there is no equal sign on the line, the entire line
54 is taken as 'name' and the variable is recognized as boolean "true".
55 The variable names are case-insensitive and only alphanumeric
56 characters and '`-`' are allowed. There can be more than one value
57 for a given variable; we say then that variable is multivalued.
59 Leading and trailing whitespace in a variable value is discarded.
60 Internal whitespace within a variable value is retained verbatim.
62 The values following the equals sign in variable assign are all either
63 a string, an integer, or a boolean. Boolean values may be given as yes/no,
64 0/1 or true/false. Case is not significant in boolean values, when
65 converting value to the canonical form using '--bool' type specifier;
66 `git-config` will ensure that the output is "true" or "false".
68 String values may be entirely or partially enclosed in double quotes.
69 You need to enclose variable value in double quotes if you want to
70 preserve leading or trailing whitespace, or if variable value contains
71 beginning of comment characters (if it contains '#' or ';').
72 Double quote '`"`' and backslash '`\`' characters in variable value must
73 be escaped: use '`\"`' for '`"`' and '`\\`' for '`\`'.
75 The following escape sequences (beside '`\"`' and '`\\`') are recognized:
76 '`\n`' for newline character (NL), '`\t`' for horizontal tabulation (HT, TAB)
77 and '`\b`' for backspace (BS). No other char escape sequence, nor octal
78 char sequences are valid.
80 Variable value ending in a '`\`' is continued on the next line in the
81 customary UNIX fashion.
83 Some variables may require special value format.
90 ; Don't trust file modes
95 external = "/usr/local/bin/gnu-diff -u"
100 merge = refs/heads/devel
104 gitProxy="ssh" for "ssh://kernel.org/"
105 gitProxy=default-proxy ; for the rest
110 Note that this list is non-comprehensive and not necessarily complete.
111 For command-specific variables, you will find a more detailed description
112 in the appropriate manual page. You will find a description of non-core
113 porcelain configuration variables in the respective porcelain documentation.
116 If false, the executable bit differences between the index and
117 the working copy are ignored; useful on broken filesystems like FAT.
118 See gitlink:git-update-index[1]. True by default.
121 The commands that output paths (e.g. `ls-files`,
122 `diff`), when not given the `-z` option, will quote
123 "unusual" characters in the pathname by enclosing the
124 pathname in a double-quote pair and with backslashes the
125 same way strings in C source code are quoted. If this
126 variable is set to false, the bytes higher than 0x80 are
127 not quoted but output as verbatim. Note that double
128 quote, backslash and control characters are always
129 quoted without `-z` regardless of the setting of this
133 If true, makes git convert `CRLF` at the end of lines in text files to
134 `LF` when reading from the filesystem, and convert in reverse when
135 writing to the filesystem. The variable can be set to
136 'input', in which case the conversion happens only while
137 reading from the filesystem but files are written out with
138 `LF` at the end of lines. Currently, which paths to consider
139 "text" (i.e. be subjected to the autocrlf mechanism) is
140 decided purely based on the contents.
143 If false, symbolic links are checked out as small plain files that
144 contain the link text. gitlink:git-update-index[1] and
145 gitlink:git-add[1] will not change the recorded type to regular
146 file. Useful on filesystems like FAT that do not support
147 symbolic links. True by default.
150 A "proxy command" to execute (as 'command host port') instead
151 of establishing direct connection to the remote server when
152 using the git protocol for fetching. If the variable value is
153 in the "COMMAND for DOMAIN" format, the command is applied only
154 on hostnames ending with the specified domain string. This variable
155 may be set multiple times and is matched in the given order;
156 the first match wins.
158 Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
159 (which always applies universally, without the special "for"
163 The working copy files are assumed to stay unchanged until you
164 mark them otherwise manually - Git will not detect the file changes
165 by lstat() calls. This is useful on systems where those are very
166 slow, such as Microsoft Windows. See gitlink:git-update-index[1].
169 core.preferSymlinkRefs::
170 Instead of the default "symref" format for HEAD
171 and other symbolic reference files, use symbolic links.
172 This is sometimes needed to work with old scripts that
173 expect HEAD to be a symbolic link.
176 If true this repository is assumed to be 'bare' and has no
177 working directory associated with it. If this is the case a
178 number of commands that require a working directory will be
179 disabled, such as gitlink:git-add[1] or gitlink:git-merge[1].
181 This setting is automatically guessed by gitlink:git-clone[1] or
182 gitlink:git-init[1] when the repository was created. By default a
183 repository that ends in "/.git" is assumed to be not bare (bare =
184 false), while all other repositories are assumed to be bare (bare
188 Set the path to the working tree. The value will not be
189 used in combination with repositories found automatically in
190 a .git directory (i.e. $GIT_DIR is not set).
191 This can be overriden by the GIT_WORK_TREE environment
192 variable and the '--work-tree' command line option.
194 core.logAllRefUpdates::
195 Updates to a ref <ref> is logged to the file
196 "$GIT_DIR/logs/<ref>", by appending the new and old
197 SHA1, the date/time and the reason of the update, but
198 only when the file exists. If this configuration
199 variable is set to true, missing "$GIT_DIR/logs/<ref>"
200 file is automatically created for branch heads.
202 This information can be used to determine what commit
203 was the tip of a branch "2 days ago".
205 This value is true by default in a repository that has
206 a working directory associated with it, and false by
207 default in a bare repository.
209 core.repositoryFormatVersion::
210 Internal variable identifying the repository format and layout
213 core.sharedRepository::
214 When 'group' (or 'true'), the repository is made shareable between
215 several users in a group (making sure all the files and objects are
216 group-writable). When 'all' (or 'world' or 'everybody'), the
217 repository will be readable by all users, additionally to being
218 group-shareable. When 'umask' (or 'false'), git will use permissions
219 reported by umask(2). See gitlink:git-init[1]. False by default.
221 core.warnAmbiguousRefs::
222 If true, git will warn you if the ref name you passed it is ambiguous
223 and might match multiple refs in the .git/refs/ tree. True by default.
226 An integer -1..9, indicating a default compression level.
227 -1 is the zlib default. 0 means no compression,
228 and 1..9 are various speed/size tradeoffs, 9 being slowest.
230 core.loosecompression::
231 An integer -1..9, indicating the compression level for objects that
232 are not in a pack file. -1 is the zlib default. 0 means no
233 compression, and 1..9 are various speed/size tradeoffs, 9 being
234 slowest. If not set, defaults to core.compression. If that is
235 not set, defaults to 0 (best speed).
237 core.packedGitWindowSize::
238 Number of bytes of a pack file to map into memory in a
239 single mapping operation. Larger window sizes may allow
240 your system to process a smaller number of large pack files
241 more quickly. Smaller window sizes will negatively affect
242 performance due to increased calls to the operating system's
243 memory manager, but may improve performance when accessing
244 a large number of large pack files.
246 Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
247 MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should
248 be reasonable for all users/operating systems. You probably do
249 not need to adjust this value.
251 Common unit suffixes of 'k', 'm', or 'g' are supported.
253 core.packedGitLimit::
254 Maximum number of bytes to map simultaneously into memory
255 from pack files. If Git needs to access more than this many
256 bytes at once to complete an operation it will unmap existing
257 regions to reclaim virtual address space within the process.
259 Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
260 This should be reasonable for all users/operating systems, except on
261 the largest projects. You probably do not need to adjust this value.
263 Common unit suffixes of 'k', 'm', or 'g' are supported.
265 core.deltaBaseCacheLimit::
266 Maximum number of bytes to reserve for caching base objects
267 that multiple deltafied objects reference. By storing the
268 entire decompressed base objects in a cache Git is able
269 to avoid unpacking and decompressing frequently used base
270 objects multiple times.
272 Default is 16 MiB on all platforms. This should be reasonable
273 for all users/operating systems, except on the largest projects.
274 You probably do not need to adjust this value.
276 Common unit suffixes of 'k', 'm', or 'g' are supported.
279 In addition to '.gitignore' (per-directory) and
280 '.git/info/exclude', git looks into this file for patterns
281 of files which are not meant to be tracked. See
282 gitlink:gitignore[5].
285 The command that git will use to paginate output. Can be overridden
286 with the `GIT_PAGER` environment variable.
289 Command aliases for the gitlink:git[1] command wrapper - e.g.
290 after defining "alias.last = cat-file commit HEAD", the invocation
291 "git last" is equivalent to "git cat-file commit HEAD". To avoid
292 confusion and troubles with script usage, aliases that
293 hide existing git commands are ignored. Arguments are split by
294 spaces, the usual shell quoting and escaping is supported.
295 quote pair and a backslash can be used to quote them.
297 If the alias expansion is prefixed with an exclamation point,
298 it will be treated as a shell command. For example, defining
299 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
300 "git new" is equivalent to running the shell command
301 "gitk --all --not ORIG_HEAD".
304 Tells `git-apply` how to handle whitespaces, in the same way
305 as the '--whitespace' option. See gitlink:git-apply[1].
307 branch.autosetupmerge::
308 Tells `git-branch` and `git-checkout` to setup new branches
309 so that gitlink:git-pull[1] will appropriately merge from that
310 remote branch. Note that even if this option is not set,
311 this behavior can be chosen per-branch using the `--track`
312 and `--no-track` options. This option can have values
313 'false' (never touch the configuration), 'all' (do this
314 for all branches), or 'true' (do this only when
315 branching from a remote tracking branch), and defaults to 'true'.
317 branch.<name>.remote::
318 When in branch <name>, it tells `git fetch` which remote to fetch.
319 If this option is not given, `git fetch` defaults to remote "origin".
321 branch.<name>.merge::
322 When in branch <name>, it tells `git fetch` the default refspec to
323 be marked for merging in FETCH_HEAD. The value has exactly to match
324 a remote part of one of the refspecs which are fetched from the remote
325 given by "branch.<name>.remote".
326 The merge information is used by `git pull` (which at first calls
327 `git fetch`) to lookup the default branch for merging. Without
328 this option, `git pull` defaults to merge the first refspec fetched.
329 Specify multiple values to get an octopus merge.
330 If you wish to setup `git pull` so that it merges into <name> from
331 another branch in the local repository, you can point
332 branch.<name>.merge to the desired branch, and use the special setting
333 `.` (a period) for branch.<name>.remote.
336 A boolean to make git-clean do nothing unless given -f or -n. Defaults
340 A boolean to enable/disable color in the output of
341 gitlink:git-branch[1]. May be set to `true` (or `always`),
342 `false` (or `never`) or `auto`, in which case colors are used
343 only when the output is to a terminal. Defaults to false.
345 color.branch.<slot>::
346 Use customized color for branch coloration. `<slot>` is one of
347 `current` (the current branch), `local` (a local branch),
348 `remote` (a tracking branch in refs/remotes/), `plain` (other
351 The value for these configuration variables is a list of colors (at most
352 two) and attributes (at most one), separated by spaces. The colors
353 accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
354 `magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
355 `blink` and `reverse`. The first color given is the foreground; the
356 second is the background. The position of the attribute, if any,
360 When true (or `always`), always use colors in patch.
361 When false (or `never`), never. When set to `auto`, use
362 colors only when the output is to the terminal.
365 Use customized color for diff colorization. `<slot>` specifies
366 which part of the patch to use the specified color, and is one
367 of `plain` (context text), `meta` (metainformation), `frag`
368 (hunk header), `old` (removed lines), `new` (added lines),
369 `commit` (commit headers), or `whitespace` (highlighting dubious
370 whitespace). The values of these variables may be specified as
371 in color.branch.<slot>.
374 A boolean to enable/disable colored output when the pager is in
375 use (default is true).
378 A boolean to enable/disable color in the output of
379 gitlink:git-status[1]. May be set to `true` (or `always`),
380 `false` (or `never`) or `auto`, in which case colors are used
381 only when the output is to a terminal. Defaults to false.
383 color.status.<slot>::
384 Use customized color for status colorization. `<slot>` is
385 one of `header` (the header text of the status message),
386 `added` or `updated` (files which are added but not committed),
387 `changed` (files which are changed but not added in the index),
388 or `untracked` (files which are not tracked by git). The values of
389 these variables may be specified as in color.branch.<slot>.
392 The number of files to consider when performing the copy/rename
393 detection; equivalent to the git diff option '-l'.
396 Tells git to detect renames. If set to any boolean value, it
397 will enable basic rename detection. If set to "copies" or
398 "copy", it will detect copies, as well.
401 If the number of objects fetched over the git native
402 transfer is below this
403 limit, then the objects will be unpacked into loose object
404 files. However if the number of received objects equals or
405 exceeds this limit then the received pack will be stored as
406 a pack, after adding any missing delta bases. Storing the
407 pack from a push can make the push operation complete faster,
408 especially on slow filesystems.
411 Additional email headers to include in a patch to be submitted
412 by mail. See gitlink:git-format-patch[1].
415 The default for format-patch is to output files with the suffix
416 `.patch`. Use this variable to change that suffix (make sure to
417 include the dot if you want it).
419 gc.aggressiveWindow::
420 The window size parameter used in the delta compression
421 algorithm used by 'git gc --aggressive'. This defaults
425 `git gc` does not run `git pack-refs` in a bare repository by
426 default so that older dumb-transport clients can still fetch
427 from the repository. Setting this to `true` lets `git
428 gc` to run `git pack-refs`. Setting this to `false` tells
429 `git gc` never to run `git pack-refs`. The default setting is
430 `notbare`. Enable it only when you know you do not have to
431 support such clients. The default setting will change to `true`
432 at some stage, and setting this to `false` will continue to
433 prevent `git pack-refs` from being run from `git gc`.
436 `git reflog expire` removes reflog entries older than
437 this time; defaults to 90 days.
439 gc.reflogexpireunreachable::
440 `git reflog expire` removes reflog entries older than
441 this time and are not reachable from the current tip;
445 Records of conflicted merge you resolved earlier are
446 kept for this many days when `git rerere gc` is run.
447 The default is 60 days. See gitlink:git-rerere[1].
449 gc.rerereunresolved::
450 Records of conflicted merge you have not resolved are
451 kept for this many days when `git rerere gc` is run.
452 The default is 15 days. See gitlink:git-rerere[1].
455 Activate recording of resolved conflicts, so that identical
456 conflict hunks can be resolved automatically, should they
457 be encountered again. See gitlink:git-rerere[1].
460 Whether the cvs server interface is enabled for this repository.
461 See gitlink:git-cvsserver[1].
464 Path to a log file where the cvs server interface well... logs
465 various stuff. See gitlink:git-cvsserver[1].
468 If true, all files are sent to the client in mode '-kb'. This
469 causes the client to treat all files as binary files which suppresses
470 any newline munging it otherwise might do. A work-around for the
471 fact that there is no way yet to set single files to mode '-kb'.
474 Database used by git-cvsserver to cache revision information
475 derived from the git repository. The exact meaning depends on the
476 used database driver, for SQLite (which is the default driver) this
477 is a filename. Supports variable substitution (see
478 gitlink:git-cvsserver[1] for details). May not contain semicolons (`;`).
479 Default: '%Ggitcvs.%m.sqlite'
482 Used Perl DBI driver. You can specify any available driver
483 for this here, but it might not work. git-cvsserver is tested
484 with 'DBD::SQLite', reported to work with 'DBD::Pg', and
485 reported *not* to work with 'DBD::mysql'. Experimental feature.
486 May not contain double colons (`:`). Default: 'SQLite'.
487 See gitlink:git-cvsserver[1].
489 gitcvs.dbuser, gitcvs.dbpass::
490 Database user and password. Only useful if setting 'gitcvs.dbdriver',
491 since SQLite has no concept of database users and/or passwords.
492 'gitcvs.dbuser' supports variable substitution (see
493 gitlink:git-cvsserver[1] for details).
495 All gitcvs variables except for 'gitcvs.allbinary' can also specifed
496 as 'gitcvs.<access_method>.<varname>' (where 'access_method' is one
497 of "ext" and "pserver") to make them apply only for the given access
501 Whether to verify the SSL certificate when fetching or pushing
502 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
506 File containing the SSL certificate when fetching or pushing
507 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
511 File containing the SSL private key when fetching or pushing
512 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
516 File containing the certificates to verify the peer with when
517 fetching or pushing over HTTPS. Can be overridden by the
518 'GIT_SSL_CAINFO' environment variable.
521 Path containing files with the CA certificates to verify the peer
522 with when fetching or pushing over HTTPS. Can be overridden
523 by the 'GIT_SSL_CAPATH' environment variable.
526 How many HTTP requests to launch in parallel. Can be overridden
527 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
529 http.lowSpeedLimit, http.lowSpeedTime::
530 If the HTTP transfer speed is less than 'http.lowSpeedLimit'
531 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
532 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
533 'GIT_HTTP_LOW_SPEED_TIME' environment variables.
536 A boolean which disables using of EPSV ftp command by curl.
537 This can helpful with some "poor" ftp servers which don't
538 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
539 environment variable. Default is false (curl will use EPSV).
541 i18n.commitEncoding::
542 Character encoding the commit messages are stored in; git itself
543 does not care per se, but this information is necessary e.g. when
544 importing commits from emails or in the gitk graphical history
545 browser (and possibly at other places in the future or in other
546 porcelains). See e.g. gitlink:git-mailinfo[1]. Defaults to 'utf-8'.
548 i18n.logOutputEncoding::
549 Character encoding the commit messages are converted to when
550 running `git-log` and friends.
553 If true, the initial commit will be shown as a big creation event.
554 This is equivalent to a diff against an empty tree.
555 Tools like gitlink:git-log[1] or gitlink:git-whatchanged[1], which
556 normally hide the root commit will now show it. True by default.
559 Whether to include summaries of merged commits in newly created
560 merge commit messages. False by default.
563 Controls which merge resolution program is used by
564 gitlink:git-mergetool[l]. Valid values are: "kdiff3", "tkdiff",
565 "meld", "xxdiff", "emerge", "vimdiff", "gvimdiff", and "opendiff".
568 Controls the amount of output shown by the recursive merge
569 strategy. Level 0 outputs nothing except a final error
570 message if conflicts were detected. Level 1 outputs only
571 conflicts, 2 outputs conflicts and file changes. Level 5 and
572 above outputs debugging information. The default is level 2.
574 merge.<driver>.name::
575 Defines a human readable name for a custom low-level
576 merge driver. See gitlink:gitattributes[5] for details.
578 merge.<driver>.driver::
579 Defines the command that implements a custom low-level
580 merge driver. See gitlink:gitattributes[5] for details.
582 merge.<driver>.recursive::
583 Names a low-level merge driver to be used when
584 performing an internal merge between common ancestors.
585 See gitlink:gitattributes[5] for details.
588 The size of the window used by gitlink:git-pack-objects[1] when no
589 window size is given on the command line. Defaults to 10.
592 The maximum delta depth used by gitlink:git-pack-objects[1] when no
593 maximum depth is given on the command line. Defaults to 50.
596 An integer -1..9, indicating the compression level for objects
597 in a pack file. -1 is the zlib default. 0 means no
598 compression, and 1..9 are various speed/size tradeoffs, 9 being
599 slowest. If not set, defaults to core.compression. If that is
600 not set, defaults to -1.
602 pack.deltaCacheSize::
603 The maxium memory in bytes used for caching deltas in
604 gitlink:git-pack-objects[1].
605 A value of 0 means no limit. Defaults to 0.
607 pack.deltaCacheLimit::
608 The maxium size of a delta, that is cached in
609 gitlink:git-pack-objects[1]. Defaults to 1000.
612 The default merge strategy to use when pulling multiple branches
616 The default merge strategy to use when pulling a single branch.
619 The URL of a remote repository. See gitlink:git-fetch[1] or
622 remote.<name>.fetch::
623 The default set of "refspec" for gitlink:git-fetch[1]. See
624 gitlink:git-fetch[1].
627 The default set of "refspec" for gitlink:git-push[1]. See
630 remote.<name>.skipDefaultUpdate::
631 If true, this remote will be skipped by default when updating
632 using the remote subcommand of gitlink:git-remote[1].
634 remote.<name>.receivepack::
635 The default program to execute on the remote side when pushing. See
636 option \--exec of gitlink:git-push[1].
638 remote.<name>.uploadpack::
639 The default program to execute on the remote side when fetching. See
640 option \--exec of gitlink:git-fetch-pack[1].
642 remote.<name>.tagopt::
643 Setting this value to --no-tags disables automatic tag following when fetching
647 The list of remotes which are fetched by "git remote update
648 <group>". See gitlink:git-remote[1].
650 repack.usedeltabaseoffset::
651 Allow gitlink:git-repack[1] to create packs that uses
652 delta-base offset. Defaults to false.
655 The default gitlink:git-diff-tree[1] arguments to be used
656 for gitlink:git-show[1].
659 The default set of branches for gitlink:git-show-branch[1].
660 See gitlink:git-show-branch[1].
663 By default, gitlink:git-tar-tree[1] sets file and directories modes
664 to 0666 or 0777. While this is both useful and acceptable for projects
665 such as the Linux Kernel, it might be excessive for other projects.
666 With this variable, it becomes possible to tell
667 gitlink:git-tar-tree[1] to apply a specific umask to the modes above.
668 The special value "user" indicates that the user's current umask will
669 be used. This should be enough for most projects, as it will lead to
670 the same permissions as gitlink:git-checkout[1] would use. The default
671 value remains 0, which means world read-write.
674 Your email address to be recorded in any newly created commits.
675 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
676 'EMAIL' environment variables. See gitlink:git-commit-tree[1].
679 Your full name to be recorded in any newly created commits.
680 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
681 environment variables. See gitlink:git-commit-tree[1].
684 If gitlink:git-tag[1] is not selecting the key you want it to
685 automatically when creating a signed tag, you can override the
686 default selection with this variable. This option is passed
687 unchanged to gpg's --local-user parameter, so you may specify a key
688 using any method that gpg supports.
690 whatchanged.difftree::
691 The default gitlink:git-diff-tree[1] arguments to be used
692 for gitlink:git-whatchanged[1].
695 The configuration variables in the 'imap' section are described
696 in gitlink:git-imap-send[1].
698 receive.unpackLimit::
699 If the number of objects received in a push is below this
700 limit then the objects will be unpacked into loose object
701 files. However if the number of received objects equals or
702 exceeds this limit then the received pack will be stored as
703 a pack, after adding any missing delta bases. Storing the
704 pack from a push can make the push operation complete faster,
705 especially on slow filesystems.
707 receive.denyNonFastForwards::
708 If set to true, git-receive-pack will deny a ref update which is
709 not a fast forward. Use this to prevent such an update via a push,
710 even if that push is forced. This configuration variable is
711 set when initializing a shared repository.
713 transfer.unpackLimit::
714 When `fetch.unpackLimit` or `receive.unpackLimit` are
715 not set, the value of this variable is used instead.