send-email: add transfer encoding header with content-type
[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 overriden 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.
229 If set, this provides a default to other compression variables,
230 such as 'core.loosecompression' and 'pack.compression'.
232 core.loosecompression::
233 An integer -1..9, indicating the compression level for objects that
234 are not in a pack file. -1 is the zlib default. 0 means no
235 compression, and 1..9 are various speed/size tradeoffs, 9 being
236 slowest. If not set, defaults to core.compression. If that is
237 not set, defaults to 1 (best speed).
239 core.packedGitWindowSize::
240 Number of bytes of a pack file to map into memory in a
241 single mapping operation. Larger window sizes may allow
242 your system to process a smaller number of large pack files
243 more quickly. Smaller window sizes will negatively affect
244 performance due to increased calls to the operating system's
245 memory manager, but may improve performance when accessing
246 a large number of large pack files.
247 +
248 Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
249 MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should
250 be reasonable for all users/operating systems. You probably do
251 not need to adjust this value.
252 +
253 Common unit suffixes of 'k', 'm', or 'g' are supported.
255 core.packedGitLimit::
256 Maximum number of bytes to map simultaneously into memory
257 from pack files. If Git needs to access more than this many
258 bytes at once to complete an operation it will unmap existing
259 regions to reclaim virtual address space within the process.
260 +
261 Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
262 This should be reasonable for all users/operating systems, except on
263 the largest projects. You probably do not need to adjust this value.
264 +
265 Common unit suffixes of 'k', 'm', or 'g' are supported.
267 core.deltaBaseCacheLimit::
268 Maximum number of bytes to reserve for caching base objects
269 that multiple deltafied objects reference. By storing the
270 entire decompressed base objects in a cache Git is able
271 to avoid unpacking and decompressing frequently used base
272 objects multiple times.
273 +
274 Default is 16 MiB on all platforms. This should be reasonable
275 for all users/operating systems, except on the largest projects.
276 You probably do not need to adjust this value.
277 +
278 Common unit suffixes of 'k', 'm', or 'g' are supported.
280 core.excludesfile::
281 In addition to '.gitignore' (per-directory) and
282 '.git/info/exclude', git looks into this file for patterns
283 of files which are not meant to be tracked. See
284 gitlink:gitignore[5].
286 core.editor::
287 Commands such as `commit` and `tag` that lets you edit
288 messages by launching an editor uses the value of this
289 variable when it is set, and the environment variable
290 `GIT_EDITOR` is not set. The order of preference is
291 `GIT_EDITOR` environment, `core.editor`, `VISUAL` and
292 `EDITOR` environment variables and then finally `vi`.
294 core.pager::
295 The command that git will use to paginate output. Can be overridden
296 with the `GIT_PAGER` environment variable.
298 alias.*::
299 Command aliases for the gitlink:git[1] command wrapper - e.g.
300 after defining "alias.last = cat-file commit HEAD", the invocation
301 "git last" is equivalent to "git cat-file commit HEAD". To avoid
302 confusion and troubles with script usage, aliases that
303 hide existing git commands are ignored. Arguments are split by
304 spaces, the usual shell quoting and escaping is supported.
305 quote pair and a backslash can be used to quote them.
306 +
307 If the alias expansion is prefixed with an exclamation point,
308 it will be treated as a shell command. For example, defining
309 " = !gitk --all --not ORIG_HEAD", the invocation
310 "git new" is equivalent to running the shell command
311 "gitk --all --not ORIG_HEAD".
313 apply.whitespace::
314 Tells `git-apply` how to handle whitespaces, in the same way
315 as the '--whitespace' option. See gitlink:git-apply[1].
317 branch.autosetupmerge::
318 Tells `git-branch` and `git-checkout` to setup new branches
319 so that gitlink:git-pull[1] will appropriately merge from that
320 remote branch. Note that even if this option is not set,
321 this behavior can be chosen per-branch using the `--track`
322 and `--no-track` options. This option defaults to false.
324 branch.<name>.remote::
325 When in branch <name>, it tells `git fetch` which remote to fetch.
326 If this option is not given, `git fetch` defaults to remote "origin".
328 branch.<name>.merge::
329 When in branch <name>, it tells `git fetch` the default refspec to
330 be marked for merging in FETCH_HEAD. The value has exactly to match
331 a remote part of one of the refspecs which are fetched from the remote
332 given by "branch.<name>.remote".
333 The merge information is used by `git pull` (which at first calls
334 `git fetch`) to lookup the default branch for merging. Without
335 this option, `git pull` defaults to merge the first refspec fetched.
336 Specify multiple values to get an octopus merge.
337 If you wish to setup `git pull` so that it merges into <name> from
338 another branch in the local repository, you can point
339 branch.<name>.merge to the desired branch, and use the special setting
340 `.` (a period) for branch.<name>.remote.
342 clean.requireForce::
343 A boolean to make git-clean do nothing unless given -f or -n. Defaults
344 to false.
346 color.branch::
347 A boolean to enable/disable color in the output of
348 gitlink:git-branch[1]. May be set to `true` (or `always`),
349 `false` (or `never`) or `auto`, in which case colors are used
350 only when the output is to a terminal. Defaults to false.
352 color.branch.<slot>::
353 Use customized color for branch coloration. `<slot>` is one of
354 `current` (the current branch), `local` (a local branch),
355 `remote` (a tracking branch in refs/remotes/), `plain` (other
356 refs).
357 +
358 The value for these configuration variables is a list of colors (at most
359 two) and attributes (at most one), separated by spaces. The colors
360 accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
361 `magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
362 `blink` and `reverse`. The first color given is the foreground; the
363 second is the background. The position of the attribute, if any,
364 doesn't matter.
366 color.diff::
367 When true (or `always`), always use colors in patch.
368 When false (or `never`), never. When set to `auto`, use
369 colors only when the output is to the terminal.
371 color.diff.<slot>::
372 Use customized color for diff colorization. `<slot>` specifies
373 which part of the patch to use the specified color, and is one
374 of `plain` (context text), `meta` (metainformation), `frag`
375 (hunk header), `old` (removed lines), `new` (added lines),
376 `commit` (commit headers), or `whitespace` (highlighting dubious
377 whitespace). The values of these variables may be specified as
378 in color.branch.<slot>.
380 color.pager::
381 A boolean to enable/disable colored output when the pager is in
382 use (default is true).
384 color.status::
385 A boolean to enable/disable color in the output of
386 gitlink:git-status[1]. May be set to `true` (or `always`),
387 `false` (or `never`) or `auto`, in which case colors are used
388 only when the output is to a terminal. Defaults to false.
390 color.status.<slot>::
391 Use customized color for status colorization. `<slot>` is
392 one of `header` (the header text of the status message),
393 `added` or `updated` (files which are added but not committed),
394 `changed` (files which are changed but not added in the index),
395 or `untracked` (files which are not tracked by git). The values of
396 these variables may be specified as in color.branch.<slot>.
398 commit.template::
399 Specify a file to use as the template for new commit messages.
401 diff.autorefreshindex::
402 When using `git diff` to compare with work tree
403 files, do not consider stat-only change as changed.
404 Instead, silently run `git update-index --refresh` to
405 update the cached stat information for paths whose
406 contents in the work tree match the contents in the
407 index. This option defaults to true. Note that this
408 affects only `git diff` Porcelain, and not lower level
409 `diff` commands, such as `git diff-files`.
411 diff.renameLimit::
412 The number of files to consider when performing the copy/rename
413 detection; equivalent to the git diff option '-l'.
415 diff.renames::
416 Tells git to detect renames. If set to any boolean value, it
417 will enable basic rename detection. If set to "copies" or
418 "copy", it will detect copies, as well.
420 fetch.unpackLimit::
421 If the number of objects fetched over the git native
422 transfer is below this
423 limit, then the objects will be unpacked into loose object
424 files. However if the number of received objects equals or
425 exceeds this limit then the received pack will be stored as
426 a pack, after adding any missing delta bases. Storing the
427 pack from a push can make the push operation complete faster,
428 especially on slow filesystems.
430 format.headers::
431 Additional email headers to include in a patch to be submitted
432 by mail. See gitlink:git-format-patch[1].
434 format.suffix::
435 The default for format-patch is to output files with the suffix
436 `.patch`. Use this variable to change that suffix (make sure to
437 include the dot if you want it).
439 gc.aggressiveWindow::
440 The window size parameter used in the delta compression
441 algorithm used by 'git gc --aggressive'. This defaults
442 to 10.
444 gc.packrefs::
445 `git gc` does not run `git pack-refs` in a bare repository by
446 default so that older dumb-transport clients can still fetch
447 from the repository. Setting this to `true` lets `git
448 gc` to run `git pack-refs`. Setting this to `false` tells
449 `git gc` never to run `git pack-refs`. The default setting is
450 `notbare`. Enable it only when you know you do not have to
451 support such clients. The default setting will change to `true`
452 at some stage, and setting this to `false` will continue to
453 prevent `git pack-refs` from being run from `git gc`.
455 gc.reflogexpire::
456 `git reflog expire` removes reflog entries older than
457 this time; defaults to 90 days.
459 gc.reflogexpireunreachable::
460 `git reflog expire` removes reflog entries older than
461 this time and are not reachable from the current tip;
462 defaults to 30 days.
464 gc.rerereresolved::
465 Records of conflicted merge you resolved earlier are
466 kept for this many days when `git rerere gc` is run.
467 The default is 60 days. See gitlink:git-rerere[1].
469 gc.rerereunresolved::
470 Records of conflicted merge you have not resolved are
471 kept for this many days when `git rerere gc` is run.
472 The default is 15 days. See gitlink:git-rerere[1].
474 rerere.enabled::
475 Activate recording of resolved conflicts, so that identical
476 conflict hunks can be resolved automatically, should they
477 be encountered again. See gitlink:git-rerere[1].
479 gitcvs.enabled::
480 Whether the CVS server interface is enabled for this repository.
481 See gitlink:git-cvsserver[1].
483 gitcvs.logfile::
484 Path to a log file where the CVS server interface well... logs
485 various stuff. See gitlink:git-cvsserver[1].
487 gitcvs.allbinary::
488 If true, all files are sent to the client in mode '-kb'. This
489 causes the client to treat all files as binary files which suppresses
490 any newline munging it otherwise might do. A work-around for the
491 fact that there is no way yet to set single files to mode '-kb'.
493 gitcvs.dbname::
494 Database used by git-cvsserver to cache revision information
495 derived from the git repository. The exact meaning depends on the
496 used database driver, for SQLite (which is the default driver) this
497 is a filename. Supports variable substitution (see
498 gitlink:git-cvsserver[1] for details). May not contain semicolons (`;`).
499 Default: '%Ggitcvs.%m.sqlite'
501 gitcvs.dbdriver::
502 Used Perl DBI driver. You can specify any available driver
503 for this here, but it might not work. git-cvsserver is tested
504 with 'DBD::SQLite', reported to work with 'DBD::Pg', and
505 reported *not* to work with 'DBD::mysql'. Experimental feature.
506 May not contain double colons (`:`). Default: 'SQLite'.
507 See gitlink:git-cvsserver[1].
509 gitcvs.dbuser, gitcvs.dbpass::
510 Database user and password. Only useful if setting 'gitcvs.dbdriver',
511 since SQLite has no concept of database users and/or passwords.
512 'gitcvs.dbuser' supports variable substitution (see
513 gitlink:git-cvsserver[1] for details).
515 All gitcvs variables except for 'gitcvs.allbinary' can also be
516 specified as 'gitcvs.<access_method>.<varname>' (where 'access_method'
517 is one of "ext" and "pserver") to make them apply only for the given
518 access method.
520 http.sslVerify::
521 Whether to verify the SSL certificate when fetching or pushing
522 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
523 variable.
525 http.sslCert::
526 File containing the SSL certificate when fetching or pushing
527 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
528 variable.
530 http.sslKey::
531 File containing the SSL private key when fetching or pushing
532 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
533 variable.
535 http.sslCAInfo::
536 File containing the certificates to verify the peer with when
537 fetching or pushing over HTTPS. Can be overridden by the
538 'GIT_SSL_CAINFO' environment variable.
540 http.sslCAPath::
541 Path containing files with the CA certificates to verify the peer
542 with when fetching or pushing over HTTPS. Can be overridden
543 by the 'GIT_SSL_CAPATH' environment variable.
545 http.maxRequests::
546 How many HTTP requests to launch in parallel. Can be overridden
547 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
549 http.lowSpeedLimit, http.lowSpeedTime::
550 If the HTTP transfer speed is less than 'http.lowSpeedLimit'
551 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
552 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
553 'GIT_HTTP_LOW_SPEED_TIME' environment variables.
555 http.noEPSV::
556 A boolean which disables using of EPSV ftp command by curl.
557 This can helpful with some "poor" ftp servers which don't
558 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
559 environment variable. Default is false (curl will use EPSV).
561 i18n.commitEncoding::
562 Character encoding the commit messages are stored in; git itself
563 does not care per se, but this information is necessary e.g. when
564 importing commits from emails or in the gitk graphical history
565 browser (and possibly at other places in the future or in other
566 porcelains). See e.g. gitlink:git-mailinfo[1]. Defaults to 'utf-8'.
568 i18n.logOutputEncoding::
569 Character encoding the commit messages are converted to when
570 running `git-log` and friends.
572 log.showroot::
573 If true, the initial commit will be shown as a big creation event.
574 This is equivalent to a diff against an empty tree.
575 Tools like gitlink:git-log[1] or gitlink:git-whatchanged[1], which
576 normally hide the root commit will now show it. True by default.
578 merge.summary::
579 Whether to include summaries of merged commits in newly created
580 merge commit messages. False by default.
582 merge.tool::
583 Controls which merge resolution program is used by
584 gitlink:git-mergetool[1]. Valid values are: "kdiff3", "tkdiff",
585 "meld", "xxdiff", "emerge", "vimdiff", "gvimdiff", and "opendiff".
587 merge.verbosity::
588 Controls the amount of output shown by the recursive merge
589 strategy. Level 0 outputs nothing except a final error
590 message if conflicts were detected. Level 1 outputs only
591 conflicts, 2 outputs conflicts and file changes. Level 5 and
592 above outputs debugging information. The default is level 2.
593 Can be overriden by 'GIT_MERGE_VERBOSITY' environment variable.
595 merge.<driver>.name::
596 Defines a human readable name for a custom low-level
597 merge driver. See gitlink:gitattributes[5] for details.
599 merge.<driver>.driver::
600 Defines the command that implements a custom low-level
601 merge driver. See gitlink:gitattributes[5] for details.
603 merge.<driver>.recursive::
604 Names a low-level merge driver to be used when
605 performing an internal merge between common ancestors.
606 See gitlink:gitattributes[5] for details.
608 pack.window::
609 The size of the window used by gitlink:git-pack-objects[1] when no
610 window size is given on the command line. Defaults to 10.
612 pack.depth::
613 The maximum delta depth used by gitlink:git-pack-objects[1] when no
614 maximum depth is given on the command line. Defaults to 50.
616 pack.windowMemory::
617 The window memory size limit used by gitlink:git-pack-objects[1]
618 when no limit is given on the command line. The value can be
619 suffixed with "k", "m", or "g". Defaults to 0, meaning no
620 limit.
622 pack.compression::
623 An integer -1..9, indicating the compression level for objects
624 in a pack file. -1 is the zlib default. 0 means no
625 compression, and 1..9 are various speed/size tradeoffs, 9 being
626 slowest. If not set, defaults to core.compression. If that is
627 not set, defaults to -1, the zlib default, which is "a default
628 compromise between speed and compression (currently equivalent
629 to level 6)."
631 pack.deltaCacheSize::
632 The maximum memory in bytes used for caching deltas in
633 gitlink:git-pack-objects[1].
634 A value of 0 means no limit. Defaults to 0.
636 pack.deltaCacheLimit::
637 The maxium size of a delta, that is cached in
638 gitlink:git-pack-objects[1]. Defaults to 1000.
640 pull.octopus::
641 The default merge strategy to use when pulling multiple branches
642 at once.
644 pull.twohead::
645 The default merge strategy to use when pulling a single branch.
647 remote.<name>.url::
648 The URL of a remote repository. See gitlink:git-fetch[1] or
649 gitlink:git-push[1].
651 remote.<name>.fetch::
652 The default set of "refspec" for gitlink:git-fetch[1]. See
653 gitlink:git-fetch[1].
655 remote.<name>.push::
656 The default set of "refspec" for gitlink:git-push[1]. See
657 gitlink:git-push[1].
659 remote.<name>.skipDefaultUpdate::
660 If true, this remote will be skipped by default when updating
661 using the remote subcommand of gitlink:git-remote[1].
663 remote.<name>.receivepack::
664 The default program to execute on the remote side when pushing. See
665 option \--exec of gitlink:git-push[1].
667 remote.<name>.uploadpack::
668 The default program to execute on the remote side when fetching. See
669 option \--exec of gitlink:git-fetch-pack[1].
671 remote.<name>.tagopt::
672 Setting this value to --no-tags disables automatic tag following when fetching
673 from remote <name>
675 remotes.<group>::
676 The list of remotes which are fetched by "git remote update
677 <group>". See gitlink:git-remote[1].
679 repack.usedeltabaseoffset::
680 Allow gitlink:git-repack[1] to create packs that uses
681 delta-base offset. Defaults to false.
683 show.difftree::
684 The default gitlink:git-diff-tree[1] arguments to be used
685 for gitlink:git-show[1].
687 showbranch.default::
688 The default set of branches for gitlink:git-show-branch[1].
689 See gitlink:git-show-branch[1].
691 tar.umask::
692 This variable can be used to restrict the permission bits of
693 tar archive entries. The default is 0002, which turns off the
694 world write bit. The special value "user" indicates that the
695 archiving user's umask will be used instead. See umask(2) and
696 gitlink:git-archive[1].
699 Your email address to be recorded in any newly created commits.
700 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
701 'EMAIL' environment variables. See gitlink:git-commit-tree[1].
704 Your full name to be recorded in any newly created commits.
705 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
706 environment variables. See gitlink:git-commit-tree[1].
708 user.signingkey::
709 If gitlink:git-tag[1] is not selecting the key you want it to
710 automatically when creating a signed tag, you can override the
711 default selection with this variable. This option is passed
712 unchanged to gpg's --local-user parameter, so you may specify a key
713 using any method that gpg supports.
715 whatchanged.difftree::
716 The default gitlink:git-diff-tree[1] arguments to be used
717 for gitlink:git-whatchanged[1].
719 imap::
720 The configuration variables in the 'imap' section are described
721 in gitlink:git-imap-send[1].
723 receive.unpackLimit::
724 If the number of objects received in a push is below this
725 limit then the objects will be unpacked into loose object
726 files. However if the number of received objects equals or
727 exceeds this limit then the received pack will be stored as
728 a pack, after adding any missing delta bases. Storing the
729 pack from a push can make the push operation complete faster,
730 especially on slow filesystems.
732 receive.denyNonFastForwards::
733 If set to true, git-receive-pack will deny a ref update which is
734 not a fast forward. Use this to prevent such an update via a push,
735 even if that push is forced. This configuration variable is
736 set when initializing a shared repository.
738 transfer.unpackLimit::
739 When `fetch.unpackLimit` or `receive.unpackLimit` are
740 not set, the value of this variable is used instead.