Merge branch 'maint' to synchronize with
[git/git.git] / Documentation / config.txt
2 ------------------
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.
18 Syntax
19 ~~~~~~
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:
36 --------
37 [section "subsection"]
39 --------
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
46 don't need to.
48 There is also (case insensitive) alternative `[section.subsection]` syntax.
49 In this syntax subsection names follow the same restrictions as for section
50 name.
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.
85 Example
86 ~~~~~~~
88 # Core variables
89 [core]
90 ; Don't trust file modes
91 filemode = false
93 # Our diff algorithm
94 [diff]
95 external = "/usr/local/bin/gnu-diff -u"
96 renames = true
98 [branch "devel"]
99 remote = origin
100 merge = refs/heads/devel
102 # Proxy settings
103 [core]
104 gitProxy="ssh" for ""
105 gitProxy=default-proxy ; for the rest
107 Variables
108 ~~~~~~~~~
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.
115 core.fileMode::
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.
120 core.quotepath::
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
130 variable.
132 core.autocrlf::
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.
142 core.symlinks::
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.
149 core.gitProxy::
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.
157 +
158 Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
159 (which always applies universally, without the special "for"
160 handling).
162 core.ignoreStat::
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].
167 False by default.
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.
175 core.bare::
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].
180 +
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
185 = true).
187 core.worktree::
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 overridden by the GIT_WORK_TREE environment
192 variable and the '--work-tree' command line option.
194 core.logAllRefUpdates::
195 Enable the reflog. 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.
201 +
202 This information can be used to determine what commit
203 was the tip of a branch "2 days ago".
204 +
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
211 version.
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.
225 core.compression::
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.
245 +
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.
250 +
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.
258 +
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.
262 +
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.
271 +
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.
275 +
276 Common unit suffixes of 'k', 'm', or 'g' are supported.
278 core.excludesfile::
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].
284 core.editor::
285 Commands such as `commit` and `tag` that lets you edit
286 messages by launching an editor uses the value of this
287 variable when it is set, and the environment variable
288 `GIT_EDITOR` is not set. The order of preference is
289 `GIT_EDITOR` environment, `core.editor`, `VISUAL` and
290 `EDITOR` environment variables and then finally `vi`.
292 core.pager::
293 The command that git will use to paginate output. Can be overridden
294 with the `GIT_PAGER` environment variable.
296 alias.*::
297 Command aliases for the gitlink:git[1] command wrapper - e.g.
298 after defining "alias.last = cat-file commit HEAD", the invocation
299 "git last" is equivalent to "git cat-file commit HEAD". To avoid
300 confusion and troubles with script usage, aliases that
301 hide existing git commands are ignored. Arguments are split by
302 spaces, the usual shell quoting and escaping is supported.
303 quote pair and a backslash can be used to quote them.
304 +
305 If the alias expansion is prefixed with an exclamation point,
306 it will be treated as a shell command. For example, defining
307 " = !gitk --all --not ORIG_HEAD", the invocation
308 "git new" is equivalent to running the shell command
309 "gitk --all --not ORIG_HEAD".
311 apply.whitespace::
312 Tells `git-apply` how to handle whitespaces, in the same way
313 as the '--whitespace' option. See gitlink:git-apply[1].
315 branch.autosetupmerge::
316 Tells `git-branch` and `git-checkout` to setup new branches
317 so that gitlink:git-pull[1] will appropriately merge from that
318 remote branch. Note that even if this option is not set,
319 this behavior can be chosen per-branch using the `--track`
320 and `--no-track` options. This option defaults to false.
322 branch.<name>.remote::
323 When in branch <name>, it tells `git fetch` which remote to fetch.
324 If this option is not given, `git fetch` defaults to remote "origin".
326 branch.<name>.merge::
327 When in branch <name>, it tells `git fetch` the default
328 refspec to be marked for merging in FETCH_HEAD. The value is
329 handled like the remote part of a refspec, and must match a
330 ref which is fetched from the remote given by
331 "branch.<name>.remote".
332 The merge information is used by `git pull` (which at first calls
333 `git fetch`) to lookup the default branch for merging. Without
334 this option, `git pull` defaults to merge the first refspec fetched.
335 Specify multiple values to get an octopus merge.
336 If you wish to setup `git pull` so that it merges into <name> from
337 another branch in the local repository, you can point
338 branch.<name>.merge to the desired branch, and use the special setting
339 `.` (a period) for branch.<name>.remote.
341 branch.<name>.mergeoptions::
342 Sets default options for merging into branch <name>. The syntax and
343 supported options are equal to that of gitlink:git-merge[1], but
344 option values containing whitespace characters are currently not
345 supported.
347 clean.requireForce::
348 A boolean to make git-clean do nothing unless given -f
349 or -n. Defaults to true.
351 color.branch::
352 A boolean to enable/disable color in the output of
353 gitlink:git-branch[1]. May be set to `true` (or `always`),
354 `false` (or `never`) or `auto`, in which case colors are used
355 only when the output is to a terminal. Defaults to false.
357 color.branch.<slot>::
358 Use customized color for branch coloration. `<slot>` is one of
359 `current` (the current branch), `local` (a local branch),
360 `remote` (a tracking branch in refs/remotes/), `plain` (other
361 refs).
362 +
363 The value for these configuration variables is a list of colors (at most
364 two) and attributes (at most one), separated by spaces. The colors
365 accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
366 `magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
367 `blink` and `reverse`. The first color given is the foreground; the
368 second is the background. The position of the attribute, if any,
369 doesn't matter.
371 color.diff::
372 When true (or `always`), always use colors in patch.
373 When false (or `never`), never. When set to `auto`, use
374 colors only when the output is to the terminal.
376 color.diff.<slot>::
377 Use customized color for diff colorization. `<slot>` specifies
378 which part of the patch to use the specified color, and is one
379 of `plain` (context text), `meta` (metainformation), `frag`
380 (hunk header), `old` (removed lines), `new` (added lines),
381 `commit` (commit headers), or `whitespace` (highlighting dubious
382 whitespace). The values of these variables may be specified as
383 in color.branch.<slot>.
385 color.pager::
386 A boolean to enable/disable colored output when the pager is in
387 use (default is true).
389 color.status::
390 A boolean to enable/disable color in the output of
391 gitlink:git-status[1]. May be set to `true` (or `always`),
392 `false` (or `never`) or `auto`, in which case colors are used
393 only when the output is to a terminal. Defaults to false.
395 color.status.<slot>::
396 Use customized color for status colorization. `<slot>` is
397 one of `header` (the header text of the status message),
398 `added` or `updated` (files which are added but not committed),
399 `changed` (files which are changed but not added in the index),
400 or `untracked` (files which are not tracked by git). The values of
401 these variables may be specified as in color.branch.<slot>.
403 commit.template::
404 Specify a file to use as the template for new commit messages.
406 diff.autorefreshindex::
407 When using `git diff` to compare with work tree
408 files, do not consider stat-only change as changed.
409 Instead, silently run `git update-index --refresh` to
410 update the cached stat information for paths whose
411 contents in the work tree match the contents in the
412 index. This option defaults to true. Note that this
413 affects only `git diff` Porcelain, and not lower level
414 `diff` commands, such as `git diff-files`.
416 diff.renameLimit::
417 The number of files to consider when performing the copy/rename
418 detection; equivalent to the git diff option '-l'.
420 diff.renames::
421 Tells git to detect renames. If set to any boolean value, it
422 will enable basic rename detection. If set to "copies" or
423 "copy", it will detect copies, as well.
425 fetch.unpackLimit::
426 If the number of objects fetched over the git native
427 transfer is below this
428 limit, then the objects will be unpacked into loose object
429 files. However if the number of received objects equals or
430 exceeds this limit then the received pack will be stored as
431 a pack, after adding any missing delta bases. Storing the
432 pack from a push can make the push operation complete faster,
433 especially on slow filesystems.
435 format.numbered::
436 A boolean which can enable sequence numbers in patch subjects.
437 Seting this option to "auto" will enable it only if there is
438 more than one patch. See --numbered option in
439 gitlink:git-format-patch[1].
441 format.headers::
442 Additional email headers to include in a patch to be submitted
443 by mail. See gitlink:git-format-patch[1].
445 format.suffix::
446 The default for format-patch is to output files with the suffix
447 `.patch`. Use this variable to change that suffix (make sure to
448 include the dot if you want it).
450 gc.aggressiveWindow::
451 The window size parameter used in the delta compression
452 algorithm used by 'git gc --aggressive'. This defaults
453 to 10.
456 When there are approximately more than this many loose
457 objects in the repository, `git gc --auto` will pack them.
458 Some Porcelain commands use this command to perform a
459 light-weight garbage collection from time to time. Setting
460 this to 0 disables it.
462 gc.autopacklimit::
463 When there are more than this many packs that are not
464 marked with `*.keep` file in the repository, `git gc
465 --auto` consolidates them into one larger pack. Setting
466 this to 0 disables this.
468 gc.packrefs::
469 `git gc` does not run `git pack-refs` in a bare repository by
470 default so that older dumb-transport clients can still fetch
471 from the repository. Setting this to `true` lets `git
472 gc` to run `git pack-refs`. Setting this to `false` tells
473 `git gc` never to run `git pack-refs`. The default setting is
474 `notbare`. Enable it only when you know you do not have to
475 support such clients. The default setting will change to `true`
476 at some stage, and setting this to `false` will continue to
477 prevent `git pack-refs` from being run from `git gc`.
479 gc.reflogexpire::
480 `git reflog expire` removes reflog entries older than
481 this time; defaults to 90 days.
483 gc.reflogexpireunreachable::
484 `git reflog expire` removes reflog entries older than
485 this time and are not reachable from the current tip;
486 defaults to 30 days.
488 gc.rerereresolved::
489 Records of conflicted merge you resolved earlier are
490 kept for this many days when `git rerere gc` is run.
491 The default is 60 days. See gitlink:git-rerere[1].
493 gc.rerereunresolved::
494 Records of conflicted merge you have not resolved are
495 kept for this many days when `git rerere gc` is run.
496 The default is 15 days. See gitlink:git-rerere[1].
498 rerere.enabled::
499 Activate recording of resolved conflicts, so that identical
500 conflict hunks can be resolved automatically, should they
501 be encountered again. See gitlink:git-rerere[1].
503 gitcvs.enabled::
504 Whether the CVS server interface is enabled for this repository.
505 See gitlink:git-cvsserver[1].
507 gitcvs.logfile::
508 Path to a log file where the CVS server interface well... logs
509 various stuff. See gitlink:git-cvsserver[1].
511 gitcvs.allbinary::
512 If true, all files are sent to the client in mode '-kb'. This
513 causes the client to treat all files as binary files which suppresses
514 any newline munging it otherwise might do. A work-around for the
515 fact that there is no way yet to set single files to mode '-kb'.
517 gitcvs.dbname::
518 Database used by git-cvsserver to cache revision information
519 derived from the git repository. The exact meaning depends on the
520 used database driver, for SQLite (which is the default driver) this
521 is a filename. Supports variable substitution (see
522 gitlink:git-cvsserver[1] for details). May not contain semicolons (`;`).
523 Default: '%Ggitcvs.%m.sqlite'
525 gitcvs.dbdriver::
526 Used Perl DBI driver. You can specify any available driver
527 for this here, but it might not work. git-cvsserver is tested
528 with 'DBD::SQLite', reported to work with 'DBD::Pg', and
529 reported *not* to work with 'DBD::mysql'. Experimental feature.
530 May not contain double colons (`:`). Default: 'SQLite'.
531 See gitlink:git-cvsserver[1].
533 gitcvs.dbuser, gitcvs.dbpass::
534 Database user and password. Only useful if setting 'gitcvs.dbdriver',
535 since SQLite has no concept of database users and/or passwords.
536 'gitcvs.dbuser' supports variable substitution (see
537 gitlink:git-cvsserver[1] for details).
539 All gitcvs variables except for 'gitcvs.allbinary' can also be
540 specified as 'gitcvs.<access_method>.<varname>' (where 'access_method'
541 is one of "ext" and "pserver") to make them apply only for the given
542 access method.
544 http.sslVerify::
545 Whether to verify the SSL certificate when fetching or pushing
546 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
547 variable.
549 http.sslCert::
550 File containing the SSL certificate when fetching or pushing
551 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
552 variable.
554 http.sslKey::
555 File containing the SSL private key when fetching or pushing
556 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
557 variable.
559 http.sslCAInfo::
560 File containing the certificates to verify the peer with when
561 fetching or pushing over HTTPS. Can be overridden by the
562 'GIT_SSL_CAINFO' environment variable.
564 http.sslCAPath::
565 Path containing files with the CA certificates to verify the peer
566 with when fetching or pushing over HTTPS. Can be overridden
567 by the 'GIT_SSL_CAPATH' environment variable.
569 http.maxRequests::
570 How many HTTP requests to launch in parallel. Can be overridden
571 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
573 http.lowSpeedLimit, http.lowSpeedTime::
574 If the HTTP transfer speed is less than 'http.lowSpeedLimit'
575 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
576 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
577 'GIT_HTTP_LOW_SPEED_TIME' environment variables.
579 http.noEPSV::
580 A boolean which disables using of EPSV ftp command by curl.
581 This can helpful with some "poor" ftp servers which don't
582 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
583 environment variable. Default is false (curl will use EPSV).
585 i18n.commitEncoding::
586 Character encoding the commit messages are stored in; git itself
587 does not care per se, but this information is necessary e.g. when
588 importing commits from emails or in the gitk graphical history
589 browser (and possibly at other places in the future or in other
590 porcelains). See e.g. gitlink:git-mailinfo[1]. Defaults to 'utf-8'.
592 i18n.logOutputEncoding::
593 Character encoding the commit messages are converted to when
594 running `git-log` and friends.
596 log.showroot::
597 If true, the initial commit will be shown as a big creation event.
598 This is equivalent to a diff against an empty tree.
599 Tools like gitlink:git-log[1] or gitlink:git-whatchanged[1], which
600 normally hide the root commit will now show it. True by default.
602 merge.summary::
603 Whether to include summaries of merged commits in newly created
604 merge commit messages. False by default.
606 merge.tool::
607 Controls which merge resolution program is used by
608 gitlink:git-mergetool[1]. Valid values are: "kdiff3", "tkdiff",
609 "meld", "xxdiff", "emerge", "vimdiff", "gvimdiff", and "opendiff".
611 merge.verbosity::
612 Controls the amount of output shown by the recursive merge
613 strategy. Level 0 outputs nothing except a final error
614 message if conflicts were detected. Level 1 outputs only
615 conflicts, 2 outputs conflicts and file changes. Level 5 and
616 above outputs debugging information. The default is level 2.
617 Can be overridden by 'GIT_MERGE_VERBOSITY' environment variable.
619 merge.<driver>.name::
620 Defines a human readable name for a custom low-level
621 merge driver. See gitlink:gitattributes[5] for details.
623 merge.<driver>.driver::
624 Defines the command that implements a custom low-level
625 merge driver. See gitlink:gitattributes[5] for details.
627 merge.<driver>.recursive::
628 Names a low-level merge driver to be used when
629 performing an internal merge between common ancestors.
630 See gitlink:gitattributes[5] for details.
632 pack.window::
633 The size of the window used by gitlink:git-pack-objects[1] when no
634 window size is given on the command line. Defaults to 10.
636 pack.depth::
637 The maximum delta depth used by gitlink:git-pack-objects[1] when no
638 maximum depth is given on the command line. Defaults to 50.
640 pack.windowMemory::
641 The window memory size limit used by gitlink:git-pack-objects[1]
642 when no limit is given on the command line. The value can be
643 suffixed with "k", "m", or "g". Defaults to 0, meaning no
644 limit.
646 pack.compression::
647 An integer -1..9, indicating the compression level for objects
648 in a pack file. -1 is the zlib default. 0 means no
649 compression, and 1..9 are various speed/size tradeoffs, 9 being
650 slowest. If not set, defaults to core.compression. If that is
651 not set, defaults to -1.
653 pack.deltaCacheSize::
654 The maximum memory in bytes used for caching deltas in
655 gitlink:git-pack-objects[1].
656 A value of 0 means no limit. Defaults to 0.
658 pack.deltaCacheLimit::
659 The maximum size of a delta, that is cached in
660 gitlink:git-pack-objects[1]. Defaults to 1000.
662 pack.threads::
663 Specifies the number of threads to spawn when searching for best
664 delta matches. This requires that gitlink:git-pack-objects[1]
665 be compiled with pthreads otherwise this option is ignored with a
666 warning. This is meant to reduce packing time on multiprocessor
667 machines. The required amount of memory for the delta search window
668 is however multiplied by the number of threads.
670 pack.indexVersion::
671 Specify the default pack index version. Valid values are 1 for
672 legacy pack index used by Git versions prior to 1.5.2, and 2 for
673 the new pack index with capabilities for packs larger than 4 GB
674 as well as proper protection against the repacking of corrupted
675 packs. Version 2 is selected and this config option ignored
676 whenever the corresponding pack is larger than 2 GB. Otherwise
677 the default is 1.
679 pull.octopus::
680 The default merge strategy to use when pulling multiple branches
681 at once.
683 pull.twohead::
684 The default merge strategy to use when pulling a single branch.
686 remote.<name>.url::
687 The URL of a remote repository. See gitlink:git-fetch[1] or
688 gitlink:git-push[1].
690 remote.<name>.fetch::
691 The default set of "refspec" for gitlink:git-fetch[1]. See
692 gitlink:git-fetch[1].
694 remote.<name>.push::
695 The default set of "refspec" for gitlink:git-push[1]. See
696 gitlink:git-push[1].
698 remote.<name>.skipDefaultUpdate::
699 If true, this remote will be skipped by default when updating
700 using the remote subcommand of gitlink:git-remote[1].
702 remote.<name>.receivepack::
703 The default program to execute on the remote side when pushing. See
704 option \--exec of gitlink:git-push[1].
706 remote.<name>.uploadpack::
707 The default program to execute on the remote side when fetching. See
708 option \--exec of gitlink:git-fetch-pack[1].
710 remote.<name>.tagopt::
711 Setting this value to --no-tags disables automatic tag following when fetching
712 from remote <name>
714 remotes.<group>::
715 The list of remotes which are fetched by "git remote update
716 <group>". See gitlink:git-remote[1].
718 repack.usedeltabaseoffset::
719 Allow gitlink:git-repack[1] to create packs that uses
720 delta-base offset. Defaults to false.
722 show.difftree::
723 The default gitlink:git-diff-tree[1] arguments to be used
724 for gitlink:git-show[1].
726 showbranch.default::
727 The default set of branches for gitlink:git-show-branch[1].
728 See gitlink:git-show-branch[1].
730 tar.umask::
731 This variable can be used to restrict the permission bits of
732 tar archive entries. The default is 0002, which turns off the
733 world write bit. The special value "user" indicates that the
734 archiving user's umask will be used instead. See umask(2) and
735 gitlink:git-archive[1].
738 Your email address to be recorded in any newly created commits.
739 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
740 'EMAIL' environment variables. See gitlink:git-commit-tree[1].
743 Your full name to be recorded in any newly created commits.
744 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
745 environment variables. See gitlink:git-commit-tree[1].
747 user.signingkey::
748 If gitlink:git-tag[1] is not selecting the key you want it to
749 automatically when creating a signed tag, you can override the
750 default selection with this variable. This option is passed
751 unchanged to gpg's --local-user parameter, so you may specify a key
752 using any method that gpg supports.
754 whatchanged.difftree::
755 The default gitlink:git-diff-tree[1] arguments to be used
756 for gitlink:git-whatchanged[1].
758 imap::
759 The configuration variables in the 'imap' section are described
760 in gitlink:git-imap-send[1].
762 receive.unpackLimit::
763 If the number of objects received in a push is below this
764 limit then the objects will be unpacked into loose object
765 files. However if the number of received objects equals or
766 exceeds this limit then the received pack will be stored as
767 a pack, after adding any missing delta bases. Storing the
768 pack from a push can make the push operation complete faster,
769 especially on slow filesystems.
771 receive.denyNonFastForwards::
772 If set to true, git-receive-pack will deny a ref update which is
773 not a fast forward. Use this to prevent such an update via a push,
774 even if that push is forced. This configuration variable is
775 set when initializing a shared repository.
777 transfer.unpackLimit::
778 When `fetch.unpackLimit` or `receive.unpackLimit` are
779 not set, the value of this variable is used instead.