| blob | 11b50fe99cc108059a3c8d6c7d6313ff3c3ca9d8 |
4 <head>
8 /* Debug borders */
10 /*
11 border: 1px solid red;
12 */
13 }
15 body {
17 }
19 a {
22 }
25 }
27 em {
29 }
31 strong {
33 }
35 tt {
37 }
45 }
49 }
50 h2 {
52 }
53 h3 {
55 }
56 h3 + * {
58 }
63 }
65 hr {
67 }
69 p {
72 }
74 pre {
77 }
79 span#author {
84 }
85 span#email {
86 }
87 span#revision {
89 }
91 div#footer {
97 }
98 div#footer-text {
101 }
102 div#footer-badges {
105 }
107 div#preamble,
114 }
118 }
122 }
124 /* Block element titles. */
131 }
134 }
138 }
141 }
144 }
150 }
154 }
159 }
163 }
167 }
170 }
179 }
183 }
188 }
192 }
198 dl {
201 }
202 dt {
206 }
209 }
213 }
216 }
220 }
221 thead {
224 }
225 tfoot {
227 }
232 }
235 }
240 }
243 }
247 }
249 div#toctitle {
256 }
261 }
265 }
269 }
273 }
275 /* Workarounds for IE6's broken and incomplete CSS2. */
281 }
287 }
293 }
297 }
302 }
304 /* IE6 sets dynamically generated links as visited. */
306 </style>
308 </head>
309 <body>
311 <h1>
312 git-config(1) Manual Page
313 </h1>
316 <p>git-config -
317 Get and set repository or global options
318 </p>
319 </div>
320 </div>
324 <div class="content"><em>git config</em> [<file-option>] [type] [-z|--null] name [value [value_regex]]
329 <em>git config</em> [<file-option>] [type] [-z|--null] --get-regexp name_regex [value_regex]
338 </div>
342 actually the section and the key separated by a dot, and the value will be
343 escaped.</p></div>
344 <div class="para"><p>Multiple lines can be added to an option by using the <em>--add</em> option.
345 If you want to update or unset an option which can occur on multiple
347 existing values that match the regexp are updated or unset. If
349 prepend a single exclamation mark in front (see also <a href="#EXAMPLES">[EXAMPLES]</a>).</p></div>
350 <div class="para"><p>The type specifier can be either <em>--int</em> or <em>--bool</em>, which will make
352 convert the value to the canonical form (simple decimal number for int,
354 no checks or transformations are performed on the value.</p></div>
355 <div class="para"><p>The file-option can be one of <em>--system</em>, <em>--global</em> or <em>--file</em>
356 which specify where the values will be read from or written to.
357 The default is to assume the config file of the current repository,
358 .git/config unless defined otherwise with GIT_DIR and GIT_CONFIG
362 <li>
363 <p>
364 The config file is invalid,
365 </p>
366 </li>
367 <li>
368 <p>
369 Can not write to the config file,
370 </p>
371 </li>
372 <li>
373 <p>
374 no section was provided,
375 </p>
376 </li>
377 <li>
378 <p>
379 the section or key is invalid,
380 </p>
381 </li>
382 <li>
383 <p>
384 you try to unset an option which does not exist,
385 </p>
386 </li>
387 <li>
388 <p>
389 you try to unset/set an option for which multiple lines match, or
390 </p>
391 </li>
392 <li>
393 <p>
395 </p>
396 </li>
397 </ol></div>
398 </div>
402 <dt>
403 --replace-all
404 </dt>
405 <dd>
406 <p>
407 Default behavior is to replace at most one line. This replaces
408 all lines matching the key (and optionally the value_regex).
409 </p>
410 </dd>
411 <dt>
412 --add
413 </dt>
414 <dd>
415 <p>
416 Adds a new line to the option without altering any existing
419 </p>
420 </dd>
421 <dt>
422 --get
423 </dt>
424 <dd>
425 <p>
426 Get the value for a given key (optionally filtered by a regex
427 matching the value). Returns error code 1 if the key was not
428 found and error code 2 if multiple key values were found.
429 </p>
430 </dd>
431 <dt>
432 --get-all
433 </dt>
434 <dd>
435 <p>
436 Like get, but does not fail if the number of values for the key
437 is not exactly one.
438 </p>
439 </dd>
440 <dt>
441 --get-regexp
442 </dt>
443 <dd>
444 <p>
445 Like --get-all, but interprets the name as a regular expression.
446 Also outputs the key names.
447 </p>
448 </dd>
449 <dt>
450 --global
451 </dt>
452 <dd>
453 <p>
454 For writing options: write to global ~/.gitconfig file rather than
455 the repository .git/config.
456 </p>
458 from all available files.</p></div>
460 </dd>
461 <dt>
462 --system
463 </dt>
464 <dd>
465 <p>
466 For writing options: write to system-wide $(prefix)/etc/gitconfig
467 rather than the repository .git/config.
468 </p>
470 rather than from all available files.</p></div>
472 </dd>
473 <dt>
474 -f config-file
475 </dt>
476 <dt>
477 --file config-file
478 </dt>
479 <dd>
480 <p>
481 Use the given config file instead of the one specified by GIT_CONFIG.
482 </p>
483 </dd>
484 <dt>
485 --remove-section
486 </dt>
487 <dd>
488 <p>
489 Remove the given section from the configuration file.
490 </p>
491 </dd>
492 <dt>
493 --rename-section
494 </dt>
495 <dd>
496 <p>
497 Rename the given section to a new name.
498 </p>
499 </dd>
500 <dt>
501 --unset
502 </dt>
503 <dd>
504 <p>
505 Remove the line matching the key from config file.
506 </p>
507 </dd>
508 <dt>
509 --unset-all
510 </dt>
511 <dd>
512 <p>
513 Remove all lines matching the key from config file.
514 </p>
515 </dd>
516 <dt>
517 -l
518 </dt>
519 <dt>
520 --list
521 </dt>
522 <dd>
523 <p>
524 List all variables set in config file.
525 </p>
526 </dd>
527 <dt>
528 --bool
529 </dt>
530 <dd>
531 <p>
533 </p>
534 </dd>
535 <dt>
536 --int
537 </dt>
538 <dd>
539 <p>
542 in the config file will cause the value to be multiplied
544 </p>
545 </dd>
546 <dt>
547 --bool-or-int
548 </dt>
549 <dd>
550 <p>
552 either --bool or --int, as described above.
553 </p>
554 </dd>
555 <dt>
556 -z
557 </dt>
558 <dt>
559 --null
560 </dt>
561 <dd>
562 <p>
563 For all options that output values and/or keys, always
564 end values with the null character (instead of a
565 newline). Use newline instead as a delimiter between
566 key and value. This allows for secure parsing of the
567 output without getting confused e.g. by values that
568 contain line breaks.
569 </p>
570 </dd>
571 <dt>
572 --get-colorbool name [stdout-is-tty]
573 </dt>
574 <dd>
575 <p>
578 "false", and is taken into account when configuration says
580 output of the command itself, and exits with status 0 if color
581 is to be used, or exits with status 1 otherwise.
584 </p>
585 </dd>
586 <dt>
587 --get-color name [default]
588 </dt>
589 <dd>
590 <p>
592 output it as the ANSI color escape sequence to the standard
595 </p>
596 </dd>
597 <dt>
598 -e
599 </dt>
600 <dt>
601 --edit
602 </dt>
603 <dd>
604 <p>
605 Opens an editor to modify the specified config file; either
607 </p>
608 </dd>
609 </dl></div>
610 </div>
616 <dt>
617 $GIT_DIR/config
618 </dt>
619 <dd>
620 <p>
621 Repository specific configuration file. (The filename is
622 of course relative to the repository root, not the working
623 directory.)
624 </p>
625 </dd>
626 <dt>
627 ~/.gitconfig
628 </dt>
629 <dd>
630 <p>
631 User-specific configuration file. Also called "global"
632 configuration file.
633 </p>
634 </dd>
635 <dt>
636 $(prefix)/etc/gitconfig
637 </dt>
638 <dd>
639 <p>
640 System-wide configuration file.
641 </p>
642 </dd>
643 </dl></div>
644 <div class="para"><p>If no further options are given, all reading options will read all of these
645 files that are available. If the global or the system-wide configuration
646 file are not available they will be ignored. If the repository configuration
648 error code. However, in neither case will an error message be issued.</p></div>
651 and <em>--unset</em>. <strong><em>git-config</em> will only ever change one file at a time</strong>.</p></div>
652 <div class="para"><p>You can override these rules either by command line options or by environment
654 to the global or system-wide file respectively. The GIT_CONFIG environment
655 variable has a similar effect, but you can specify any filename you want.</p></div>
656 </div>
660 <dt>
661 GIT_CONFIG
662 </dt>
663 <dd>
664 <p>
665 Take the configuration from the given file instead of .git/config.
666 Using the "--global" option forces this to ~/.gitconfig. Using the
667 "--system" option forces this to $(prefix)/etc/gitconfig.
668 </p>
669 </dd>
670 </dl></div>
672 </div>
678 <pre><tt>#
679 # This is the config file, and
680 # a '#' or ';' character indicates
681 # a comment
682 #</tt></pre>
683 </div></div>
686 <pre><tt>; core variables
687 [core]
688 ; Don't trust file modes
689 filemode = false</tt></pre>
690 </div></div>
693 <pre><tt>; Our diff algorithm
694 [diff]
695 external = /usr/local/bin/diff-wrapper
696 renames = true</tt></pre>
697 </div></div>
700 <pre><tt>; Proxy settings
701 [core]
703 gitproxy=default-proxy ; for all the rest</tt></pre>
704 </div></div>
709 </div></div>
711 what URL they apply to. Here is how to change the entry for kernel.org
716 </div></div>
717 <div class="para"><p>This makes sure that only the key/value pair for kernel.org is replaced.</p></div>
722 </div></div>
724 you have to provide a regex matching the value of exactly one line.</p></div>
729 </div></div>
734 </div></div>
739 </div></div>
744 </div></div>
745 <div class="para"><p>If you like to live dangerously, you can replace <strong>all</strong> core.gitproxy by a
746 new one with</p></div>
750 </div></div>
751 <div class="para"><p>However, if you really only want to replace the line for the default proxy,
756 </div></div>
757 <div class="para"><p>To actually match only values with an exclamation mark, you have to</p></div>
761 </div></div>
762 <div class="para"><p>To add a new proxy, without altering any of the existing ones, use</p></div>
766 </div></div>
768 script:</p></div>
771 <pre><tt>#!/bin/sh
772 WS=$(git config --get-color color.diff.whitespace "blue reverse")
775 </div></div>
776 </div>
781 is used to store the configuration for that repository, and
784 can be used to store a system-wide default configuration.</p></div>
786 and the porcelains. The variables are divided into sections, wherein
787 the fully qualified variable name of the variable itself is the last
788 dot-separated segment and the section name is everything before the last
789 dot. The variable names are case-insensitive and only alphanumeric
790 characters are allowed. Some variables may appear multiple times.</p></div>
794 blank lines are ignored.</p></div>
796 the name of the section in square brackets and continues until the next
797 section begins. Section names are not case sensitive. Only alphanumeric
799 must belong to some section, which means that there must be a section
800 header before the first setting of a variable.</p></div>
802 put its name in double quotes, separated by space from the section name,
803 in the section header, like in the example below:</p></div>
807 </tt></pre>
808 </div></div>
810 newline (doublequote <tt>"</tt> and backslash have to be escaped as <tt>\"</tt> and <tt>\\</tt>,
811 respectively). Section headers cannot span multiple
812 lines. Variables may belong directly to a section or to a given subsection.
814 don't need to.</p></div>
815 <div class="para"><p>There is also a case insensitive alternative <tt>[section.subsection]</tt> syntax.
816 In this syntax, subsection names follow the same restrictions as for section
817 names.</p></div>
819 header) are recognized as setting variables, in the form
822 The variable names are case-insensitive and only alphanumeric
824 for a given variable; we say then that variable is multivalued.</p></div>
826 Internal whitespace within a variable value is retained verbatim.</p></div>
828 a string, an integer, or a boolean. Boolean values may be given as yes/no,
833 You need to enclose variable values in double quotes if you want to
834 preserve leading or trailing whitespace, or if the variable value contains
838 <div class="para"><p>The following escape sequences (beside <tt>\"</tt> and <tt>\\</tt>) are recognized:
841 char sequences are valid.</p></div>
842 <div class="para"><p>Variable values ending in a <tt>\</tt> are continued on the next line in the
843 customary UNIX fashion.</p></div>
848 <pre><tt># Core variables
849 [core]
850 ; Don't trust file modes
851 filemode = false</tt></pre>
852 </div></div>
855 <pre><tt># Our diff algorithm
856 [diff]
857 external = /usr/local/bin/diff-wrapper
858 renames = true</tt></pre>
859 </div></div>
863 remote = origin
864 merge = refs/heads/devel</tt></pre>
865 </div></div>
868 <pre><tt># Proxy settings
869 [core]
871 gitProxy=default-proxy ; for the rest</tt></pre>
872 </div></div>
875 For command-specific variables, you will find a more detailed description
876 in the appropriate manual page. You will find a description of non-core
877 porcelain configuration variables in the respective porcelain documentation.</p></div>
879 <dt>
880 advice.*
881 </dt>
882 <dd>
883 <p>
886 are:
887 </p>
889 <dt>
890 pushNonFastForward
891 </dt>
892 <dd>
893 <p>
895 non-fast-forward refs. Default: true.
896 </p>
897 </dd>
898 <dt>
899 statusHints
900 </dt>
901 <dd>
902 <p>
903 Directions on how to stage/unstage/add shown in the
905 when writing commit messages. Default: true.
906 </p>
907 </dd>
908 </dl></div>
909 </dd>
910 <dt>
911 core.fileMode
912 </dt>
913 <dd>
914 <p>
915 If false, the executable bit differences between the index and
916 the working copy are ignored; useful on broken filesystems like FAT.
918 </p>
919 </dd>
920 <dt>
921 core.ignoreCygwinFSTricks
922 </dt>
923 <dd>
924 <p>
925 This option is only used by Cygwin implementation of Git. If false,
926 the Cygwin stat() and lstat() functions are used. This may be useful
927 if your repository consists of a few separate directories joined in
928 one hierarchy using Cygwin mount. If true, Git uses native Win32 API
929 whenever it is possible and falls back to Cygwin functions only to
930 handle symbol links. The native mode is more than twice faster than
931 normal Cygwin l/stat() functions. True by default, unless core.filemode
932 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's
933 POSIX emulation is required to support core.filemode.
934 </p>
935 </dd>
936 <dt>
937 core.trustctime
938 </dt>
939 <dd>
940 <p>
941 If false, the ctime differences between the index and the
942 working copy are ignored; useful when the inode change time
943 is regularly modified by something outside Git (file system
944 crawlers and some backup systems).
946 </p>
947 </dd>
948 <dt>
949 core.quotepath
950 </dt>
951 <dd>
952 <p>
955 "unusual" characters in the pathname by enclosing the
956 pathname in a double-quote pair and with backslashes the
957 same way strings in C source code are quoted. If this
958 variable is set to false, the bytes higher than 0x80 are
959 not quoted but output as verbatim. Note that double
960 quote, backslash and control characters are always
962 variable.
963 </p>
964 </dd>
965 <dt>
966 core.autocrlf
967 </dt>
968 <dd>
969 <p>
972 writing to the filesystem. The variable can be set to
974 reading from the filesystem but files are written out with
976 "text" (i.e. be subjected to the autocrlf mechanism) is
977 decided purely based on the contents.
978 </p>
979 </dd>
980 <dt>
981 core.safecrlf
982 </dt>
983 <dd>
984 <p>
987 modifies a file in the work tree either directly or indirectly.
988 For example, committing a file followed by checking out the
989 same file should yield the original file in the work tree. If
990 this is not the case for the current setting of
992 be set to "warn", in which case git will only warn about an
993 irreversible conversion but continue the operation.
994 </p>
996 autocrlf=true will convert CRLF to LF during commit and LF to
997 CRLF during checkout. A file that contains a mixture of LF and
998 CRLF before the commit cannot be recreated by git. For text
999 files this is the right thing to do: it corrects line endings
1000 such that we have only LF line endings in the repository.
1001 But for binary files that are accidentally classified as text the
1002 conversion can corrupt data.</p></div>
1004 setting the conversion type explicitly in .gitattributes. Right
1005 after committing you still have the original file in your work
1006 tree and this file is not yet corrupted. You can explicitly tell
1007 git that this file is binary and git will handle the file
1008 appropriately.</p></div>
1010 mixed line endings and the undesired effect of corrupting binary
1011 files cannot be distinguished. In both cases CRLFs are removed
1012 in an irreversible way. For text files this is the right thing
1013 to do because CRLFs are line endings, while for binary files
1014 converting CRLFs corrupts data.</p></div>
1016 file identical to the original file for a different setting of
1024 mechanism.</p></div>
1025 </dd>
1026 <dt>
1027 core.symlinks
1028 </dt>
1029 <dd>
1030 <p>
1031 If false, symbolic links are checked out as small plain files that
1034 file. Useful on filesystems like FAT that do not support
1035 symbolic links. True by default.
1036 </p>
1037 </dd>
1038 <dt>
1039 core.gitProxy
1040 </dt>
1041 <dd>
1042 <p>
1044 of establishing direct connection to the remote server when
1045 using the git protocol for fetching. If the variable value is
1046 in the "COMMAND for DOMAIN" format, the command is applied only
1047 on hostnames ending with the specified domain string. This variable
1048 may be set multiple times and is matched in the given order;
1049 the first match wins.
1050 </p>
1052 (which always applies universally, without the special "for"
1053 handling).</p></div>
1055 specify that no proxy be used for a given domain pattern.
1056 This is useful for excluding servers inside a firewall from
1057 proxy use, while defaulting to a common proxy for external domains.</p></div>
1058 </dd>
1059 <dt>
1060 core.ignoreStat
1061 </dt>
1062 <dd>
1063 <p>
1064 If true, commands which modify both the working tree and the index
1065 will mark the updated paths with the "assume unchanged" bit in the
1066 index. These marked files are then assumed to stay unchanged in the
1067 working copy, until you mark them otherwise manually - Git will not
1068 detect the file changes by lstat() calls. This is useful on systems
1069 where those are very slow, such as Microsoft Windows.
1071 False by default.
1072 </p>
1073 </dd>
1074 <dt>
1075 core.preferSymlinkRefs
1076 </dt>
1077 <dd>
1078 <p>
1079 Instead of the default "symref" format for HEAD
1080 and other symbolic reference files, use symbolic links.
1081 This is sometimes needed to work with old scripts that
1082 expect HEAD to be a symbolic link.
1083 </p>
1084 </dd>
1085 <dt>
1086 core.bare
1087 </dt>
1088 <dd>
1089 <p>
1091 working directory associated with it. If this is the case a
1092 number of commands that require a working directory will be
1093 disabled, such as <a href="git-add.html">git-add(1)</a> or <a href="git-merge.html">git-merge(1)</a>.
1094 </p>
1095 <div class="para"><p>This setting is automatically guessed by <a href="git-clone.html">git-clone(1)</a> or
1097 repository that ends in "/.git" is assumed to be not bare (bare =
1098 false), while all other repositories are assumed to be bare (bare
1099 = true).</p></div>
1100 </dd>
1101 <dt>
1102 core.worktree
1103 </dt>
1104 <dd>
1105 <p>
1106 Set the path to the working tree. The value will not be
1107 used in combination with repositories found automatically in
1108 a .git directory (i.e. $GIT_DIR is not set).
1109 This can be overridden by the GIT_WORK_TREE environment
1111 a absolute path or relative path to the directory specified by
1112 --git-dir or GIT_DIR.
1113 Note: If --git-dir or GIT_DIR are specified but none of
1114 --work-tree, GIT_WORK_TREE and core.worktree is specified,
1115 the current working directory is regarded as the top directory
1116 of your working tree.
1117 </p>
1118 </dd>
1119 <dt>
1120 core.logAllRefUpdates
1121 </dt>
1122 <dd>
1123 <p>
1125 "$GIT_DIR/logs/<ref>", by appending the new and old
1126 SHA1, the date/time and the reason of the update, but
1127 only when the file exists. If this configuration
1128 variable is set to true, missing "$GIT_DIR/logs/<ref>"
1129 file is automatically created for branch heads.
1130 </p>
1134 a working directory associated with it, and false by
1135 default in a bare repository.</p></div>
1136 </dd>
1137 <dt>
1138 core.repositoryFormatVersion
1139 </dt>
1140 <dd>
1141 <p>
1142 Internal variable identifying the repository format and layout
1143 version.
1144 </p>
1145 </dd>
1146 <dt>
1147 core.sharedRepository
1148 </dt>
1149 <dd>
1150 <p>
1152 several users in a group (making sure all the files and objects are
1154 repository will be readable by all users, additionally to being
1158 user's umask value (whereas the other options will only override
1160 the repo read/write-able for the owner and group, but inaccessible to
1162 repository that is group-readable but not group-writable.
1164 </p>
1165 </dd>
1166 <dt>
1167 core.warnAmbiguousRefs
1168 </dt>
1169 <dd>
1170 <p>
1171 If true, git will warn you if the ref name you passed it is ambiguous
1172 and might match multiple refs in the .git/refs/ tree. True by default.
1173 </p>
1174 </dd>
1175 <dt>
1176 core.compression
1177 </dt>
1178 <dd>
1179 <p>
1183 If set, this provides a default to other compression variables,
1185 </p>
1186 </dd>
1187 <dt>
1188 core.loosecompression
1189 </dt>
1190 <dd>
1191 <p>
1195 slowest. If not set, defaults to core.compression. If that is
1196 not set, defaults to 1 (best speed).
1197 </p>
1198 </dd>
1199 <dt>
1200 core.packedGitWindowSize
1201 </dt>
1202 <dd>
1203 <p>
1204 Number of bytes of a pack file to map into memory in a
1205 single mapping operation. Larger window sizes may allow
1206 your system to process a smaller number of large pack files
1207 more quickly. Smaller window sizes will negatively affect
1208 performance due to increased calls to the operating system's
1209 memory manager, but may improve performance when accessing
1210 a large number of large pack files.
1211 </p>
1214 be reasonable for all users/operating systems. You probably do
1215 not need to adjust this value.</p></div>
1216 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1217 </dd>
1218 <dt>
1219 core.packedGitLimit
1220 </dt>
1221 <dd>
1222 <p>
1223 Maximum number of bytes to map simultaneously into memory
1224 from pack files. If Git needs to access more than this many
1225 bytes at once to complete an operation it will unmap existing
1226 regions to reclaim virtual address space within the process.
1227 </p>
1229 This should be reasonable for all users/operating systems, except on
1230 the largest projects. You probably do not need to adjust this value.</p></div>
1231 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1232 </dd>
1233 <dt>
1234 core.deltaBaseCacheLimit
1235 </dt>
1236 <dd>
1237 <p>
1238 Maximum number of bytes to reserve for caching base objects
1239 that multiple deltafied objects reference. By storing the
1240 entire decompressed base objects in a cache Git is able
1241 to avoid unpacking and decompressing frequently used base
1242 objects multiple times.
1243 </p>
1245 for all users/operating systems, except on the largest projects.
1246 You probably do not need to adjust this value.</p></div>
1247 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1248 </dd>
1249 <dt>
1250 core.excludesfile
1251 </dt>
1252 <dd>
1253 <p>
1256 of files which are not meant to be tracked. See
1258 </p>
1259 </dd>
1260 <dt>
1261 core.editor
1262 </dt>
1263 <dd>
1264 <p>
1266 messages by launching an editor uses the value of this
1267 variable when it is set, and the environment variable
1271 </p>
1272 </dd>
1273 <dt>
1274 core.pager
1275 </dt>
1276 <dd>
1277 <p>
1278 The command that git will use to paginate output. Can
1282 pager. One can change these settings by setting the
1284 these settings can be overridden on a project or
1287 environment variable behaviour above, so if you want
1288 to override git's default settings this way, you need
1289 to be explicit. For example, to disable the S option
1292 shell by git, which will translate the final command to
1294 </p>
1295 </dd>
1296 <dt>
1297 core.whitespace
1298 </dt>
1299 <dd>
1300 <p>
1301 A comma separated list of common whitespace problems to
1306 </p>
1308 <li>
1309 <p>
1311 as an error (enabled by default).
1312 </p>
1313 </li>
1314 <li>
1315 <p>
1317 before a tab character in the initial indent part of the line as an
1318 error (enabled by default).
1319 </p>
1320 </li>
1321 <li>
1322 <p>
1324 space characters as an error (not enabled by default).
1325 </p>
1326 </li>
1327 <li>
1328 <p>
1330 (enabled by default).
1331 </p>
1332 </li>
1333 <li>
1334 <p>
1337 </p>
1338 </li>
1339 <li>
1340 <p>
1343 does not trigger if the character before such a carriage-return
1344 is not a whitespace (not enabled by default).
1345 </p>
1346 </li>
1347 </ul></div>
1348 </dd>
1349 <dt>
1350 core.fsyncobjectfiles
1351 </dt>
1352 <dd>
1353 <p>
1355 </p>
1357 data writes properly, but can be useful for filesystems that do not use
1358 journalling (traditional UNIX filesystems) or that only journal metadata
1360 </dd>
1361 <dt>
1362 core.preloadindex
1363 </dt>
1364 <dd>
1365 <p>
1367 </p>
1368 <div class="para"><p>This can speed up operations like <em>git diff</em> and <em>git status</em> especially
1369 on filesystems like NFS that have weak caching semantics and thus
1371 index comparison to the filesystem data in parallel, allowing
1372 overlapping IO's.</p></div>
1373 </dd>
1374 <dt>
1375 core.createObject
1376 </dt>
1377 <dd>
1378 <p>
1380 a delete of the source are used to make sure that object creation
1381 will not overwrite existing objects.
1382 </p>
1385 check that makes sure that existing object files will not get overwritten.</p></div>
1386 </dd>
1387 <dt>
1388 add.ignore-errors
1389 </dt>
1390 <dd>
1391 <p>
1395 </p>
1396 </dd>
1397 <dt>
1398 alias.*
1399 </dt>
1400 <dd>
1401 <p>
1403 after defining "alias.last = cat-file commit HEAD", the invocation
1405 confusion and troubles with script usage, aliases that
1406 hide existing git commands are ignored. Arguments are split by
1407 spaces, the usual shell quoting and escaping is supported.
1408 quote pair and a backslash can be used to quote them.
1409 </p>
1411 it will be treated as a shell command. For example, defining
1412 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
1413 "git new" is equivalent to running the shell command
1414 "gitk --all --not ORIG_HEAD". Note that shell commands will be
1415 executed from the top-level directory of a repository, which may
1416 not necessarily be the current directory.</p></div>
1417 </dd>
1418 <dt>
1419 apply.ignorewhitespace
1420 </dt>
1421 <dd>
1422 <p>
1425 option.
1427 respect all whitespace differences.
1429 </p>
1430 </dd>
1431 <dt>
1432 apply.whitespace
1433 </dt>
1434 <dd>
1435 <p>
1438 </p>
1439 </dd>
1440 <dt>
1441 branch.autosetupmerge
1442 </dt>
1443 <dd>
1444 <p>
1447 starting point branch. Note that even if this option is not set,
1452 done when the starting point is either a local branch or remote
1453 branch. This option defaults to true.
1454 </p>
1455 </dd>
1456 <dt>
1457 branch.autosetuprebase
1458 </dt>
1459 <dd>
1460 <p>
1462 that tracks another branch, this variable tells git to set
1463 up pull to rebase instead of merge (see "branch.<name>.rebase").
1466 other local branches.
1468 remote branches.
1470 branches.
1471 See "branch.autosetupmerge" for details on how to set up a
1472 branch to track another branch.
1473 This option defaults to never.
1474 </p>
1475 </dd>
1476 <dt>
1478 </dt>
1479 <dd>
1480 <p>
1484 </p>
1485 </dd>
1486 <dt>
1488 </dt>
1489 <dd>
1490 <p>
1495 refspec to be marked for merging in FETCH_HEAD. The value is
1496 handled like the remote part of a refspec, and must match a
1497 ref which is fetched from the remote given by
1498 "branch.<name>.remote".
1502 Specify multiple values to get an octopus merge.
1504 another branch in the local repository, you can point
1507 </p>
1508 </dd>
1509 <dt>
1511 </dt>
1512 <dd>
1513 <p>
1516 option values containing whitespace characters are currently not
1517 supported.
1518 </p>
1519 </dd>
1520 <dt>
1522 </dt>
1523 <dd>
1524 <p>
1526 instead of merging the default branch from the default remote when
1527 "git pull" is run.
1530 for details).
1531 </p>
1532 </dd>
1533 <dt>
1535 </dt>
1536 <dd>
1537 <p>
1538 Specify the command to invoke the specified browser. The
1539 specified command is evaluated in shell with the URLs passed
1541 </p>
1542 </dd>
1543 <dt>
1545 </dt>
1546 <dd>
1547 <p>
1548 Override the path for the given tool that may be used to
1551 </p>
1552 </dd>
1553 <dt>
1554 clean.requireForce
1555 </dt>
1556 <dd>
1557 <p>
1558 A boolean to make git-clean do nothing unless given -f
1559 or -n. Defaults to true.
1560 </p>
1561 </dd>
1562 <dt>
1563 color.branch
1564 </dt>
1565 <dd>
1566 <p>
1567 A boolean to enable/disable color in the output of
1569 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1570 only when the output is to a terminal. Defaults to false.
1571 </p>
1572 </dd>
1573 <dt>
1575 </dt>
1576 <dd>
1577 <p>
1581 refs).
1582 </p>
1584 two) and attributes (at most one), separated by spaces. The colors
1585 accepted are <tt>normal</tt>, <tt>black</tt>, <tt>red</tt>, <tt>green</tt>, <tt>yellow</tt>, <tt>blue</tt>,
1586 <tt>magenta</tt>, <tt>cyan</tt> and <tt>white</tt>; the attributes are <tt>bold</tt>, <tt>dim</tt>, <tt>ul</tt>,
1588 second is the background. The position of the attribute, if any,
1589 doesn't matter.</p></div>
1590 </dd>
1591 <dt>
1592 color.diff
1593 </dt>
1594 <dd>
1595 <p>
1598 colors only when the output is to the terminal. Defaults to false.
1599 </p>
1600 </dd>
1601 <dt>
1603 </dt>
1604 <dd>
1605 <p>
1607 which part of the patch to use the specified color, and is one
1611 whitespace errors). The values of these variables may be specified as
1613 </p>
1614 </dd>
1615 <dt>
1616 color.grep
1617 </dt>
1618 <dd>
1619 <p>
1623 </p>
1624 </dd>
1625 <dt>
1626 color.grep.external
1627 </dt>
1628 <dd>
1629 <p>
1631 command as a command line option if match highlighting is turned
1632 on. If set to an empty string, no option is passed at all,
1635 when a pager is used.
1636 </p>
1637 </dd>
1638 <dt>
1639 color.grep.match
1640 </dt>
1641 <dd>
1642 <p>
1643 Use customized color for matches. The value of this variable
1647 </p>
1648 </dd>
1649 <dt>
1650 color.interactive
1651 </dt>
1652 <dd>
1653 <p>
1655 and displays (such as those used by "git-add --interactive").
1657 colors only when the output is to the terminal. Defaults to false.
1658 </p>
1659 </dd>
1660 <dt>
1662 </dt>
1663 <dd>
1664 <p>
1666 output. <tt><slot></tt> may be <tt>prompt</tt>, <tt>header</tt>, <tt>help</tt> or <tt>error</tt>, for
1667 four distinct types of normal output from interactive
1668 commands. The values of these variables may be specified as
1670 </p>
1671 </dd>
1672 <dt>
1673 color.pager
1674 </dt>
1675 <dd>
1676 <p>
1677 A boolean to enable/disable colored output when the pager is in
1678 use (default is true).
1679 </p>
1680 </dd>
1681 <dt>
1682 color.showbranch
1683 </dt>
1684 <dd>
1685 <p>
1686 A boolean to enable/disable color in the output of
1688 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1689 only when the output is to a terminal. Defaults to false.
1690 </p>
1691 </dd>
1692 <dt>
1693 color.status
1694 </dt>
1695 <dd>
1696 <p>
1697 A boolean to enable/disable color in the output of
1699 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1700 only when the output is to a terminal. Defaults to false.
1701 </p>
1702 </dd>
1703 <dt>
1705 </dt>
1706 <dd>
1707 <p>
1714 to red). The values of these variables may be specified as in
1716 </p>
1717 </dd>
1718 <dt>
1719 color.ui
1720 </dt>
1721 <dd>
1722 <p>
1726 terminal. When more specific variables of color.* are set, they always
1727 take precedence over this setting. Defaults to false.
1728 </p>
1729 </dd>
1730 <dt>
1731 commit.template
1732 </dt>
1733 <dd>
1734 <p>
1735 Specify a file to use as the template for new commit messages.
1736 </p>
1737 </dd>
1738 <dt>
1739 diff.autorefreshindex
1740 </dt>
1741 <dd>
1742 <p>
1744 files, do not consider stat-only change as changed.
1746 update the cached stat information for paths whose
1747 contents in the work tree match the contents in the
1748 index. This option defaults to true. Note that this
1751 </p>
1752 </dd>
1753 <dt>
1754 diff.external
1755 </dt>
1756 <dd>
1757 <p>
1758 If this config variable is set, diff generation is not
1759 performed using the internal diff machinery, but using the
1760 given command. Can be overridden with the `GIT_EXTERNAL_DIFF'
1761 environment variable. The command is called with parameters
1763 you want to use an external diff program only on a subset of
1765 </p>
1766 </dd>
1767 <dt>
1768 diff.mnemonicprefix
1769 </dt>
1770 <dd>
1771 <p>
1774 this configuration is in effect, reverse diff output also swaps
1775 the order of the prefixes:
1776 </p>
1778 <dt>
1780 </dt>
1781 <dd>
1782 <p>
1783 compares the (i)ndex and the (w)ork tree;
1784 </p>
1785 </dd>
1786 <dt>
1788 </dt>
1789 <dd>
1790 <p>
1791 compares a (c)ommit and the (w)ork tree;
1792 </p>
1793 </dd>
1794 <dt>
1796 </dt>
1797 <dd>
1798 <p>
1799 compares a (c)ommit and the (i)ndex;
1800 </p>
1801 </dd>
1802 <dt>
1804 </dt>
1805 <dd>
1806 <p>
1807 compares an (o)bject and a (w)ork tree entity;
1808 </p>
1809 </dd>
1810 <dt>
1812 </dt>
1813 <dd>
1814 <p>
1816 </p>
1817 </dd>
1818 </dl></div>
1819 </dd>
1820 <dt>
1821 diff.renameLimit
1822 </dt>
1823 <dd>
1824 <p>
1825 The number of files to consider when performing the copy/rename
1827 </p>
1828 </dd>
1829 <dt>
1830 diff.renames
1831 </dt>
1832 <dd>
1833 <p>
1834 Tells git to detect renames. If set to any boolean value, it
1835 will enable basic rename detection. If set to "copies" or
1836 "copy", it will detect copies, as well.
1837 </p>
1838 </dd>
1839 <dt>
1840 diff.suppressBlankEmpty
1841 </dt>
1842 <dd>
1843 <p>
1844 A boolean to inhibit the standard behavior of printing a space
1845 before each empty output line. Defaults to false.
1846 </p>
1847 </dd>
1848 <dt>
1849 diff.tool
1850 </dt>
1851 <dd>
1852 <p>
1856 and plus "kompare".
1857 </p>
1858 </dd>
1859 <dt>
1861 </dt>
1862 <dd>
1863 <p>
1864 Override the path for the given tool. This is useful in case
1865 your tool is not in the PATH.
1866 </p>
1867 </dd>
1868 <dt>
1870 </dt>
1871 <dd>
1872 <p>
1873 Specify the command to invoke the specified diff tool.
1874 The specified command is evaluated in shell with the following
1877 is set to the name of the temporary file containing the contents
1878 of the diff post-image.
1879 </p>
1880 </dd>
1881 <dt>
1882 difftool.prompt
1883 </dt>
1884 <dd>
1885 <p>
1886 Prompt before each invocation of the diff tool.
1887 </p>
1888 </dd>
1889 <dt>
1890 diff.wordRegex
1891 </dt>
1892 <dd>
1893 <p>
1894 A POSIX Extended Regular Expression used to determine what is a "word"
1895 when performing word-by-word difference calculations. Character
1896 sequences that match the regular expression are "words", all other
1898 </p>
1899 </dd>
1900 <dt>
1901 fetch.unpackLimit
1902 </dt>
1903 <dd>
1904 <p>
1905 If the number of objects fetched over the git native
1906 transfer is below this
1907 limit, then the objects will be unpacked into loose object
1908 files. However if the number of received objects equals or
1909 exceeds this limit then the received pack will be stored as
1910 a pack, after adding any missing delta bases. Storing the
1911 pack from a push can make the push operation complete faster,
1912 especially on slow filesystems. If not set, the value of
1914 </p>
1915 </dd>
1916 <dt>
1917 format.attach
1918 </dt>
1919 <dd>
1920 <p>
1921 Enable multipart/mixed attachments as the default for
1923 which will enable attachments as the default and set the
1924 value as the boundary. See the --attach option in
1926 </p>
1927 </dd>
1928 <dt>
1929 format.numbered
1930 </dt>
1931 <dd>
1932 <p>
1933 A boolean which can enable or disable sequence numbers in patch
1934 subjects. It defaults to "auto" which enables it only if there
1935 is more than one patch. It can be enabled or disabled for all
1938 </p>
1939 </dd>
1940 <dt>
1941 format.headers
1942 </dt>
1943 <dd>
1944 <p>
1945 Additional email headers to include in a patch to be submitted
1947 </p>
1948 </dd>
1949 <dt>
1950 format.cc
1951 </dt>
1952 <dd>
1953 <p>
1954 Additional "Cc:" headers to include in a patch to be submitted
1956 </p>
1957 </dd>
1958 <dt>
1959 format.subjectprefix
1960 </dt>
1961 <dd>
1962 <p>
1964 subject prefix. Use this variable to change that prefix.
1965 </p>
1966 </dd>
1967 <dt>
1968 format.suffix
1969 </dt>
1970 <dd>
1971 <p>
1972 The default for format-patch is to output files with the suffix
1974 include the dot if you want it).
1975 </p>
1976 </dd>
1977 <dt>
1978 format.pretty
1979 </dt>
1980 <dd>
1981 <p>
1982 The default pretty format for log/show/whatchanged command,
1985 </p>
1986 </dd>
1987 <dt>
1988 format.thread
1989 </dt>
1990 <dd>
1991 <p>
1994 threading makes every mail a reply to the head of the series,
1995 where the head is chosen from the cover letter, the
1999 value disables threading.
2000 </p>
2001 </dd>
2002 <dt>
2003 format.signoff
2004 </dt>
2005 <dd>
2006 <p>
2009 patch should be a conscious act and means that you certify you have
2010 the rights to submit this work under the same open source license.
2012 </p>
2013 </dd>
2014 <dt>
2015 gc.aggressiveWindow
2016 </dt>
2017 <dd>
2018 <p>
2019 The window size parameter used in the delta compression
2021 to 10.
2022 </p>
2023 </dd>
2024 <dt>
2025 gc.auto
2026 </dt>
2027 <dd>
2028 <p>
2029 When there are approximately more than this many loose
2031 Some Porcelain commands use this command to perform a
2032 light-weight garbage collection from time to time. The
2034 </p>
2035 </dd>
2036 <dt>
2037 gc.autopacklimit
2038 </dt>
2039 <dd>
2040 <p>
2041 When there are more than this many packs that are not
2043 --auto</tt> consolidates them into one larger pack. The
2045 </p>
2046 </dd>
2047 <dt>
2048 gc.packrefs
2049 </dt>
2050 <dd>
2051 <p>
2053 default so that older dumb-transport clients can still fetch
2061 </p>
2062 </dd>
2063 <dt>
2064 gc.pruneexpire
2065 </dt>
2066 <dd>
2067 <p>
2069 Override the grace period with this config variable. The value
2070 "now" may be used to disable this grace period and always prune
2071 unreachable objects immediately.
2072 </p>
2073 </dd>
2074 <dt>
2075 gc.reflogexpire
2076 </dt>
2077 <dd>
2078 <p>
2080 this time; defaults to 90 days.
2081 </p>
2082 </dd>
2083 <dt>
2084 gc.reflogexpireunreachable
2085 </dt>
2086 <dd>
2087 <p>
2089 this time and are not reachable from the current tip;
2090 defaults to 30 days.
2091 </p>
2092 </dd>
2093 <dt>
2094 gc.rerereresolved
2095 </dt>
2096 <dd>
2097 <p>
2098 Records of conflicted merge you resolved earlier are
2101 </p>
2102 </dd>
2103 <dt>
2104 gc.rerereunresolved
2105 </dt>
2106 <dd>
2107 <p>
2108 Records of conflicted merge you have not resolved are
2111 </p>
2112 </dd>
2113 <dt>
2114 gitcvs.commitmsgannotation
2115 </dt>
2116 <dd>
2117 <p>
2118 Append this string to each commit message. Set to empty string
2119 to disable this feature. Defaults to "via git-CVS emulator".
2120 </p>
2121 </dd>
2122 <dt>
2123 gitcvs.enabled
2124 </dt>
2125 <dd>
2126 <p>
2127 Whether the CVS server interface is enabled for this repository.
2129 </p>
2130 </dd>
2131 <dt>
2132 gitcvs.logfile
2133 </dt>
2134 <dd>
2135 <p>
2136 Path to a log file where the CVS server interface well… logs
2138 </p>
2139 </dd>
2140 <dt>
2141 gitcvs.usecrlfattr
2142 </dt>
2143 <dd>
2144 <p>
2152 </p>
2153 </dd>
2154 <dt>
2155 gitcvs.allbinary
2156 </dt>
2157 <dd>
2158 <p>
2161 unresolved files are sent to the client in
2163 as binary files, which suppresses any newline munging it
2164 otherwise might do. Alternatively, if it is set to "guess",
2165 then the contents of the file are examined to decide if
2167 </p>
2168 </dd>
2169 <dt>
2170 gitcvs.dbname
2171 </dt>
2172 <dd>
2173 <p>
2174 Database used by git-cvsserver to cache revision information
2175 derived from the git repository. The exact meaning depends on the
2176 used database driver, for SQLite (which is the default driver) this
2177 is a filename. Supports variable substitution (see
2178 <a href="git-cvsserver.html">git-cvsserver(1)</a> for details). May not contain semicolons (<tt>;</tt>).
2180 </p>
2181 </dd>
2182 <dt>
2183 gitcvs.dbdriver
2184 </dt>
2185 <dd>
2186 <p>
2187 Used Perl DBI driver. You can specify any available driver
2188 for this here, but it might not work. git-cvsserver is tested
2193 </p>
2194 </dd>
2195 <dt>
2196 gitcvs.dbuser, gitcvs.dbpass
2197 </dt>
2198 <dd>
2199 <p>
2201 since SQLite has no concept of database users and/or passwords.
2204 </p>
2205 </dd>
2206 <dt>
2207 gitcvs.dbTableNamePrefix
2208 </dt>
2209 <dd>
2210 <p>
2211 Database table name prefix. Prepended to the names of any
2212 database tables used, allowing a single database to be used
2213 for several repositories. Supports variable substitution (see
2215 characters will be replaced with underscores.
2216 </p>
2217 </dd>
2218 </dl></div>
2223 access method.</p></div>
2225 <dt>
2226 gui.commitmsgwidth
2227 </dt>
2228 <dd>
2229 <p>
2230 Defines how wide the commit message window is in the
2232 </p>
2233 </dd>
2234 <dt>
2235 gui.diffcontext
2236 </dt>
2237 <dd>
2238 <p>
2239 Specifies how many context lines should be used in calls to diff
2241 </p>
2242 </dd>
2243 <dt>
2244 gui.encoding
2245 </dt>
2246 <dd>
2247 <p>
2248 Specifies the default encoding to use for displaying of
2252 If this option is not set, the tools default to the
2253 locale encoding.
2254 </p>
2255 </dd>
2256 <dt>
2257 gui.matchtrackingbranch
2258 </dt>
2259 <dd>
2260 <p>
2262 default to tracking remote branches with matching names or
2263 not. Default: "false".
2264 </p>
2265 </dd>
2266 <dt>
2267 gui.newbranchtemplate
2268 </dt>
2269 <dd>
2270 <p>
2271 Is used as suggested name when creating new branches using the
2273 </p>
2274 </dd>
2275 <dt>
2276 gui.pruneduringfetch
2277 </dt>
2278 <dd>
2279 <p>
2281 performing a fetch. The default value is "false".
2282 </p>
2283 </dd>
2284 <dt>
2285 gui.trustmtime
2286 </dt>
2287 <dd>
2288 <p>
2290 timestamp or not. By default the timestamps are not trusted.
2291 </p>
2292 </dd>
2293 <dt>
2294 gui.spellingdictionary
2295 </dt>
2296 <dd>
2297 <p>
2298 Specifies the dictionary used for spell checking commit messages in
2300 off.
2301 </p>
2302 </dd>
2303 <dt>
2304 gui.fastcopyblame
2305 </dt>
2306 <dd>
2307 <p>
2309 location detection. It makes blame significantly faster on huge
2310 repositories at the expense of less thorough copy detection.
2311 </p>
2312 </dd>
2313 <dt>
2314 gui.copyblamethreshold
2315 </dt>
2316 <dd>
2317 <p>
2319 detection, measured in alphanumeric characters. See the
2321 </p>
2322 </dd>
2323 <dt>
2324 gui.blamehistoryctx
2325 </dt>
2326 <dd>
2327 <p>
2328 Specifies the radius of history context in days to show in
2331 variable is set to zero, the whole history is shown.
2332 </p>
2333 </dd>
2334 <dt>
2336 </dt>
2337 <dd>
2338 <p>
2339 Specifies the shell command line to execute when the corresponding item
2341 mandatory for every tool. The command is executed from the root of
2342 the working directory, and in the environment it receives the name of
2346 </p>
2347 </dd>
2348 <dt>
2350 </dt>
2351 <dd>
2352 <p>
2353 Run the tool only if a diff is selected in the GUI. It guarantees
2355 </p>
2356 </dd>
2357 <dt>
2359 </dt>
2360 <dd>
2361 <p>
2362 Run the command silently, without creating a window to display its
2363 output.
2364 </p>
2365 </dd>
2366 <dt>
2368 </dt>
2369 <dd>
2370 <p>
2371 Don't rescan the working directory for changes after the tool
2372 finishes execution.
2373 </p>
2374 </dd>
2375 <dt>
2377 </dt>
2378 <dd>
2379 <p>
2380 Show a confirmation dialog before actually running the tool.
2381 </p>
2382 </dd>
2383 <dt>
2385 </dt>
2386 <dd>
2387 <p>
2388 Request a string argument from the user, and pass it to the tool
2392 the dialog uses a built-in generic prompt; otherwise the exact
2393 value of the variable is used.
2394 </p>
2395 </dd>
2396 <dt>
2398 </dt>
2399 <dd>
2400 <p>
2401 Request a single valid revision from the user, and set the
2404 </p>
2405 </dd>
2406 <dt>
2408 </dt>
2409 <dd>
2410 <p>
2412 This is useful for tools similar to merge or rebase, but not
2413 for things like checkout or reset.
2414 </p>
2415 </dd>
2416 <dt>
2418 </dt>
2419 <dd>
2420 <p>
2421 Specifies the title to use for the prompt dialog. The default
2422 is the tool name.
2423 </p>
2424 </dd>
2425 <dt>
2427 </dt>
2428 <dd>
2429 <p>
2430 Specifies the general prompt string to display at the top of
2432 The default value includes the actual command.
2433 </p>
2434 </dd>
2435 <dt>
2436 help.browser
2437 </dt>
2438 <dd>
2439 <p>
2440 Specify the browser that will be used to display help in the
2442 </p>
2443 </dd>
2444 <dt>
2445 help.format
2446 </dt>
2447 <dd>
2448 <p>
2450 Values <em>man</em>, <em>info</em>, <em>web</em> and <em>html</em> are supported. <em>man</em> is
2452 </p>
2453 </dd>
2454 <dt>
2455 help.autocorrect
2456 </dt>
2457 <dd>
2458 <p>
2459 Automatically correct and execute mistyped commands after
2460 waiting for the given number of deciseconds (0.1 sec). If more
2461 than one command can be deduced from the entered text, nothing
2462 will be executed. If the value of this option is negative,
2463 the corrected command will be executed immediately. If the
2464 value is 0 - the command will be just shown but not executed.
2465 This is the default.
2466 </p>
2467 </dd>
2468 <dt>
2469 http.proxy
2470 </dt>
2471 <dd>
2472 <p>
2476 </p>
2477 </dd>
2478 <dt>
2479 http.sslVerify
2480 </dt>
2481 <dd>
2482 <p>
2483 Whether to verify the SSL certificate when fetching or pushing
2485 variable.
2486 </p>
2487 </dd>
2488 <dt>
2489 http.sslCert
2490 </dt>
2491 <dd>
2492 <p>
2493 File containing the SSL certificate when fetching or pushing
2495 variable.
2496 </p>
2497 </dd>
2498 <dt>
2499 http.sslKey
2500 </dt>
2501 <dd>
2502 <p>
2503 File containing the SSL private key when fetching or pushing
2505 variable.
2506 </p>
2507 </dd>
2508 <dt>
2509 http.sslCertPasswordProtected
2510 </dt>
2511 <dd>
2512 <p>
2513 Enable git's password prompt for the SSL certificate. Otherwise
2514 OpenSSL will prompt the user, possibly many times, if the
2515 certificate or private key is encrypted. Can be overridden by the
2517 </p>
2518 </dd>
2519 <dt>
2520 http.sslCAInfo
2521 </dt>
2522 <dd>
2523 <p>
2524 File containing the certificates to verify the peer with when
2525 fetching or pushing over HTTPS. Can be overridden by the
2527 </p>
2528 </dd>
2529 <dt>
2530 http.sslCAPath
2531 </dt>
2532 <dd>
2533 <p>
2534 Path containing files with the CA certificates to verify the peer
2535 with when fetching or pushing over HTTPS. Can be overridden
2537 </p>
2538 </dd>
2539 <dt>
2540 http.maxRequests
2541 </dt>
2542 <dd>
2543 <p>
2544 How many HTTP requests to launch in parallel. Can be overridden
2546 </p>
2547 </dd>
2548 <dt>
2549 http.lowSpeedLimit, http.lowSpeedTime
2550 </dt>
2551 <dd>
2552 <p>
2557 </p>
2558 </dd>
2559 <dt>
2560 http.noEPSV
2561 </dt>
2562 <dd>
2563 <p>
2564 A boolean which disables using of EPSV ftp command by curl.
2565 This can helpful with some "poor" ftp servers which don't
2567 environment variable. Default is false (curl will use EPSV).
2568 </p>
2569 </dd>
2570 <dt>
2571 i18n.commitEncoding
2572 </dt>
2573 <dd>
2574 <p>
2575 Character encoding the commit messages are stored in; git itself
2576 does not care per se, but this information is necessary e.g. when
2577 importing commits from emails or in the gitk graphical history
2578 browser (and possibly at other places in the future or in other
2579 porcelains). See e.g. <a href="git-mailinfo.html">git-mailinfo(1)</a>. Defaults to <em>utf-8</em>.
2580 </p>
2581 </dd>
2582 <dt>
2583 i18n.logOutputEncoding
2584 </dt>
2585 <dd>
2586 <p>
2587 Character encoding the commit messages are converted to when
2589 </p>
2590 </dd>
2591 <dt>
2592 imap
2593 </dt>
2594 <dd>
2595 <p>
2598 </p>
2599 </dd>
2600 <dt>
2601 instaweb.browser
2602 </dt>
2603 <dd>
2604 <p>
2605 Specify the program that will be used to browse your working
2607 </p>
2608 </dd>
2609 <dt>
2610 instaweb.httpd
2611 </dt>
2612 <dd>
2613 <p>
2614 The HTTP daemon command-line to start gitweb on your working
2616 </p>
2617 </dd>
2618 <dt>
2619 instaweb.local
2620 </dt>
2621 <dd>
2622 <p>
2624 be bound to the local IP (127.0.0.1).
2625 </p>
2626 </dd>
2627 <dt>
2628 instaweb.modulepath
2629 </dt>
2630 <dd>
2631 <p>
2633 </p>
2634 </dd>
2635 <dt>
2636 instaweb.port
2637 </dt>
2638 <dd>
2639 <p>
2640 The port number to bind the gitweb httpd to. See
2642 </p>
2643 </dd>
2644 <dt>
2645 interactive.singlekey
2646 </dt>
2647 <dd>
2648 <p>
2649 In interactive commands, allow the user to provide one-letter
2650 input with a single key (i.e., without hitting enter).
2653 ignored if portable keystroke input is not available.
2654 </p>
2655 </dd>
2656 <dt>
2657 log.date
2658 </dt>
2659 <dd>
2660 <p>
2661 Set default date-time mode for the log command. Setting log.date
2663 following alternatives: {relative,local,default,iso,rfc,short}.
2665 </p>
2666 </dd>
2667 <dt>
2668 log.showroot
2669 </dt>
2670 <dd>
2671 <p>
2672 If true, the initial commit will be shown as a big creation event.
2673 This is equivalent to a diff against an empty tree.
2674 Tools like <a href="git-log.html">git-log(1)</a> or <a href="git-whatchanged.html">git-whatchanged(1)</a>, which
2675 normally hide the root commit will now show it. True by default.
2676 </p>
2677 </dd>
2678 <dt>
2679 mailmap.file
2680 </dt>
2681 <dd>
2682 <p>
2683 The location of an augmenting mailmap file. The default
2684 mailmap, located in the root of the repository, is loaded
2685 first, then the mailmap file pointed to by this variable.
2686 The location of the mailmap file may be in a repository
2687 subdirectory, or somewhere outside of the repository itself.
2688 See <a href="git-shortlog.html">git-shortlog(1)</a> and <a href="git-blame.html">git-blame(1)</a>.
2689 </p>
2690 </dd>
2691 <dt>
2692 man.viewer
2693 </dt>
2694 <dd>
2695 <p>
2696 Specify the programs that may be used to display help in the
2698 </p>
2699 </dd>
2700 <dt>
2702 </dt>
2703 <dd>
2704 <p>
2705 Specify the command to invoke the specified man viewer. The
2706 specified command is evaluated in shell with the man page
2708 </p>
2709 </dd>
2710 <dt>
2712 </dt>
2713 <dd>
2714 <p>
2715 Override the path for the given tool that may be used to
2717 </p>
2718 </dd>
2719 <dt>
2720 merge.conflictstyle
2721 </dt>
2722 <dd>
2723 <p>
2724 Specify the style in which conflicted hunks are written out to
2725 working tree files upon merge. The default is "merge", which
2728 a <tt>>>>>>>></tt> marker. An alternate style, "diff3", adds a <tt>|||||||</tt>
2730 </p>
2731 </dd>
2732 <dt>
2733 merge.log
2734 </dt>
2735 <dd>
2736 <p>
2737 Whether to include summaries of merged commits in newly created
2738 merge commit messages. False by default.
2739 </p>
2740 </dd>
2741 <dt>
2742 merge.renameLimit
2743 </dt>
2744 <dd>
2745 <p>
2746 The number of files to consider when performing rename detection
2747 during a merge; if not specified, defaults to the value of
2748 diff.renameLimit.
2749 </p>
2750 </dd>
2751 <dt>
2752 merge.stat
2753 </dt>
2754 <dd>
2755 <p>
2756 Whether to print the diffstat between ORIG_HEAD and the merge result
2757 at the end of the merge. True by default.
2758 </p>
2759 </dd>
2760 <dt>
2761 merge.tool
2762 </dt>
2763 <dd>
2764 <p>
2765 Controls which merge resolution program is used by
2769 "opendiff". Any other value is treated is custom merge tool
2771 </p>
2772 </dd>
2773 <dt>
2774 merge.verbosity
2775 </dt>
2776 <dd>
2777 <p>
2778 Controls the amount of output shown by the recursive merge
2779 strategy. Level 0 outputs nothing except a final error
2780 message if conflicts were detected. Level 1 outputs only
2782 above outputs debugging information. The default is level 2.
2784 </p>
2785 </dd>
2786 <dt>
2788 </dt>
2789 <dd>
2790 <p>
2791 Defines a human-readable name for a custom low-level
2793 </p>
2794 </dd>
2795 <dt>
2797 </dt>
2798 <dd>
2799 <p>
2800 Defines the command that implements a custom low-level
2802 </p>
2803 </dd>
2804 <dt>
2806 </dt>
2807 <dd>
2808 <p>
2809 Names a low-level merge driver to be used when
2810 performing an internal merge between common ancestors.
2812 </p>
2813 </dd>
2814 <dt>
2816 </dt>
2817 <dd>
2818 <p>
2819 Override the path for the given tool. This is useful in case
2820 your tool is not in the PATH.
2821 </p>
2822 </dd>
2823 <dt>
2825 </dt>
2826 <dd>
2827 <p>
2828 Specify the command to invoke the specified merge tool. The
2829 specified command is evaluated in shell with the following
2831 containing the common base of the files to be merged, if available;
2834 file containing the contents of the file from the branch being
2836 tool should write the results of a successful merge.
2837 </p>
2838 </dd>
2839 <dt>
2841 </dt>
2842 <dd>
2843 <p>
2844 For a custom merge command, specify whether the exit code of
2845 the merge command can be used to determine whether the merge was
2846 successful. If this is not set to true then the merge target file
2847 timestamp is checked and the merge assumed to have been successful
2848 if the file has been updated, otherwise the user is prompted to
2849 indicate the success of the merge.
2850 </p>
2851 </dd>
2852 <dt>
2853 mergetool.keepBackup
2854 </dt>
2855 <dd>
2856 <p>
2857 After performing a merge, the original file with conflict markers
2861 </p>
2862 </dd>
2863 <dt>
2864 mergetool.keepTemporaries
2865 </dt>
2866 <dd>
2867 <p>
2868 When invoking a custom merge tool, git uses a set of temporary
2869 files to pass to the tool. If the tool returns an error and this
2871 preserved, otherwise they will be removed after the tool has
2873 </p>
2874 </dd>
2875 <dt>
2876 mergetool.prompt
2877 </dt>
2878 <dd>
2879 <p>
2880 Prompt before each invocation of the merge resolution program.
2881 </p>
2882 </dd>
2883 <dt>
2884 pack.window
2885 </dt>
2886 <dd>
2887 <p>
2889 window size is given on the command line. Defaults to 10.
2890 </p>
2891 </dd>
2892 <dt>
2893 pack.depth
2894 </dt>
2895 <dd>
2896 <p>
2897 The maximum delta depth used by <a href="git-pack-objects.html">git-pack-objects(1)</a> when no
2898 maximum depth is given on the command line. Defaults to 50.
2899 </p>
2900 </dd>
2901 <dt>
2902 pack.windowMemory
2903 </dt>
2904 <dd>
2905 <p>
2907 when no limit is given on the command line. The value can be
2909 limit.
2910 </p>
2911 </dd>
2912 <dt>
2913 pack.compression
2914 </dt>
2915 <dd>
2916 <p>
2920 slowest. If not set, defaults to core.compression. If that is
2922 compromise between speed and compression (currently equivalent
2923 to level 6)."
2924 </p>
2925 </dd>
2926 <dt>
2927 pack.deltaCacheSize
2928 </dt>
2929 <dd>
2930 <p>
2931 The maximum memory in bytes used for caching deltas in
2933 This cache is used to speed up the writing object phase by not
2934 having to recompute the final delta result once the best match
2935 for all objects is found. Repacking large repositories on machines
2936 which are tight with memory might be badly impacted by this though,
2937 especially if this cache pushes the system into swapping.
2939 used to virtually disable this cache. Defaults to 256 MiB.
2940 </p>
2941 </dd>
2942 <dt>
2943 pack.deltaCacheLimit
2944 </dt>
2945 <dd>
2946 <p>
2947 The maximum size of a delta, that is cached in
2949 writing object phase by not having to recompute the final delta
2950 result once the best match for all objects is found. Defaults to 1000.
2951 </p>
2952 </dd>
2953 <dt>
2954 pack.threads
2955 </dt>
2956 <dd>
2957 <p>
2958 Specifies the number of threads to spawn when searching for best
2960 be compiled with pthreads otherwise this option is ignored with a
2961 warning. This is meant to reduce packing time on multiprocessor
2962 machines. The required amount of memory for the delta search window
2963 is however multiplied by the number of threads.
2964 Specifying 0 will cause git to auto-detect the number of CPU's
2965 and set the number of threads accordingly.
2966 </p>
2967 </dd>
2968 <dt>
2969 pack.indexVersion
2970 </dt>
2971 <dd>
2972 <p>
2973 Specify the default pack index version. Valid values are 1 for
2975 the new pack index with capabilities for packs larger than 4 GB
2976 as well as proper protection against the repacking of corrupted
2978 and this config option ignored whenever the corresponding pack is
2979 larger than 2 GB.
2980 </p>
2981 <div class="para"><p>If you have an old git that does not understand the version 2 <tt>*.idx</tt> file,
2983 that will copy both <tt>*.pack</tt> file and corresponding <tt>*.idx</tt> file from the
2984 other side may give you a repository that cannot be accessed with your
2986 you can use <a href="git-index-pack.html">git-index-pack(1)</a> on the *.pack file to regenerate
2988 </dd>
2989 <dt>
2990 pack.packSizeLimit
2991 </dt>
2992 <dd>
2993 <p>
2994 The default maximum size of a pack. This setting only affects
2995 packing to a file, i.e. the git:// protocol is unaffected. It
2998 </p>
2999 </dd>
3000 <dt>
3002 </dt>
3003 <dd>
3004 <p>
3005 Allows turning on or off pagination of the output of a
3006 particular git subcommand when writing to a tty. If
3008 it takes precedence over this option. To disable pagination for
3010 </p>
3011 </dd>
3012 <dt>
3013 pull.octopus
3014 </dt>
3015 <dd>
3016 <p>
3017 The default merge strategy to use when pulling multiple branches
3018 at once.
3019 </p>
3020 </dd>
3021 <dt>
3022 pull.twohead
3023 </dt>
3024 <dd>
3025 <p>
3026 The default merge strategy to use when pulling a single branch.
3027 </p>
3028 </dd>
3029 <dt>
3030 push.default
3031 </dt>
3032 <dd>
3033 <p>
3034 Defines the action git push should take if no refspec is given
3035 on the command line, no refspec is configured in the remote, and
3036 no refspec is implied by any of the options given on the command
3037 line. Possible values are:
3038 </p>
3040 <li>
3041 <p>
3043 </p>
3044 </li>
3045 <li>
3046 <p>
3048 All branches having the same name in both ends are considered to be
3049 matching. This is the default.
3050 </p>
3051 </li>
3052 <li>
3053 <p>
3055 </p>
3056 </li>
3057 <li>
3058 <p>
3060 </p>
3061 </li>
3062 </ul></div>
3063 </dd>
3064 <dt>
3065 rebase.stat
3066 </dt>
3067 <dd>
3068 <p>
3069 Whether to show a diffstat of what changed upstream since the last
3070 rebase. False by default.
3071 </p>
3072 </dd>
3073 <dt>
3074 receive.autogc
3075 </dt>
3076 <dd>
3077 <p>
3078 By default, git-receive-pack will run "git-gc --auto" after
3079 receiving data from git-push and updating refs. You can stop
3080 it by setting this variable to false.
3081 </p>
3082 </dd>
3083 <dt>
3084 receive.fsckObjects
3085 </dt>
3086 <dd>
3087 <p>
3088 If it is set to true, git-receive-pack will check all received
3089 objects. It will abort in the case of a malformed object or a
3090 broken link. The result of an abort are only dangling objects.
3091 Defaults to false.
3092 </p>
3093 </dd>
3094 <dt>
3095 receive.unpackLimit
3096 </dt>
3097 <dd>
3098 <p>
3099 If the number of objects received in a push is below this
3100 limit then the objects will be unpacked into loose object
3101 files. However if the number of received objects equals or
3102 exceeds this limit then the received pack will be stored as
3103 a pack, after adding any missing delta bases. Storing the
3104 pack from a push can make the push operation complete faster,
3105 especially on slow filesystems. If not set, the value of
3107 </p>
3108 </dd>
3109 <dt>
3110 receive.denyDeletes
3111 </dt>
3112 <dd>
3113 <p>
3114 If set to true, git-receive-pack will deny a ref update that deletes
3115 the ref. Use this to prevent such a ref deletion via a push.
3116 </p>
3117 </dd>
3118 <dt>
3119 receive.denyCurrentBranch
3120 </dt>
3121 <dd>
3122 <p>
3123 If set to true or "refuse", receive-pack will deny a ref update
3124 to the currently checked out branch of a non-bare repository.
3125 Such a push is potentially dangerous because it brings the HEAD
3126 out of sync with the index and working tree. If set to "warn",
3127 print a warning of such a push to stderr, but allow the push to
3128 proceed. If set to false or "ignore", allow such pushes with no
3129 message. Defaults to "warn".
3130 </p>
3131 </dd>
3132 <dt>
3133 receive.denyNonFastForwards
3134 </dt>
3135 <dd>
3136 <p>
3137 If set to true, git-receive-pack will deny a ref update which is
3138 not a fast forward. Use this to prevent such an update via a push,
3139 even if that push is forced. This configuration variable is
3140 set when initializing a shared repository.
3141 </p>
3142 </dd>
3143 <dt>
3144 receive.updateserverinfo
3145 </dt>
3146 <dd>
3147 <p>
3148 If set to true, git-receive-pack will run git-update-server-info
3149 after receiving data from git-push and updating refs.
3150 </p>
3151 </dd>
3152 <dt>
3154 </dt>
3155 <dd>
3156 <p>
3159 </p>
3160 </dd>
3161 <dt>
3163 </dt>
3164 <dd>
3165 <p>
3167 </p>
3168 </dd>
3169 <dt>
3171 </dt>
3172 <dd>
3173 <p>
3174 For remotes that require curl (http, https and ftp), the URL to
3175 the proxy to use for that remote. Set to the empty string to
3176 disable proxying for that remote.
3177 </p>
3178 </dd>
3179 <dt>
3181 </dt>
3182 <dd>
3183 <p>
3186 </p>
3187 </dd>
3188 <dt>
3190 </dt>
3191 <dd>
3192 <p>
3195 </p>
3196 </dd>
3197 <dt>
3199 </dt>
3200 <dd>
3201 <p>
3202 If true, pushing to this remote will automatically behave
3204 </p>
3205 </dd>
3206 <dt>
3208 </dt>
3209 <dd>
3210 <p>
3211 If true, this remote will be skipped by default when updating
3213 </p>
3214 </dd>
3215 <dt>
3217 </dt>
3218 <dd>
3219 <p>
3220 The default program to execute on the remote side when pushing. See
3222 </p>
3223 </dd>
3224 <dt>
3226 </dt>
3227 <dd>
3228 <p>
3229 The default program to execute on the remote side when fetching. See
3231 </p>
3232 </dd>
3233 <dt>
3235 </dt>
3236 <dd>
3237 <p>
3238 Setting this value to --no-tags disables automatic tag following when
3240 </p>
3241 </dd>
3242 <dt>
3244 </dt>
3245 <dd>
3246 <p>
3247 The list of remotes which are fetched by "git remote update
3249 </p>
3250 </dd>
3251 <dt>
3252 repack.usedeltabaseoffset
3253 </dt>
3254 <dd>
3255 <p>
3257 delta-base offset. If you need to share your repository with
3258 git older than version 1.4.4, either directly or via a dumb
3259 protocol such as http, then you need to set this option to
3260 "false" and repack. Access from old git versions over the
3261 native protocol are unaffected by this option.
3262 </p>
3263 </dd>
3264 <dt>
3265 rerere.autoupdate
3266 </dt>
3267 <dd>
3268 <p>
3270 resulting contents after it cleanly resolves conflicts using
3271 previously recorded resolution. Defaults to false.
3272 </p>
3273 </dd>
3274 <dt>
3275 rerere.enabled
3276 </dt>
3277 <dd>
3278 <p>
3279 Activate recording of resolved conflicts, so that identical
3280 conflict hunks can be resolved automatically, should they
3284 </p>
3285 </dd>
3286 <dt>
3287 sendemail.identity
3288 </dt>
3289 <dd>
3290 <p>
3291 A configuration identity. When given, causes values in the
3295 </p>
3296 </dd>
3297 <dt>
3298 sendemail.smtpencryption
3299 </dt>
3300 <dd>
3301 <p>
3304 </p>
3305 </dd>
3306 <dt>
3307 sendemail.smtpssl
3308 </dt>
3309 <dd>
3310 <p>
3312 </p>
3313 </dd>
3314 <dt>
3316 </dt>
3317 <dd>
3318 <p>
3320 found below, taking precedence over those when the this
3321 identity is selected, through command-line or
3323 </p>
3324 </dd>
3325 <dt>
3326 sendemail.aliasesfile
3327 </dt>
3328 <dt>
3329 sendemail.aliasfiletype
3330 </dt>
3331 <dt>
3332 sendemail.bcc
3333 </dt>
3334 <dt>
3335 sendemail.cc
3336 </dt>
3337 <dt>
3338 sendemail.cccmd
3339 </dt>
3340 <dt>
3341 sendemail.chainreplyto
3342 </dt>
3343 <dt>
3344 sendemail.confirm
3345 </dt>
3346 <dt>
3347 sendemail.envelopesender
3348 </dt>
3349 <dt>
3350 sendemail.from
3351 </dt>
3352 <dt>
3353 sendemail.multiedit
3354 </dt>
3355 <dt>
3356 sendemail.signedoffbycc
3357 </dt>
3358 <dt>
3359 sendemail.smtppass
3360 </dt>
3361 <dt>
3362 sendemail.suppresscc
3363 </dt>
3364 <dt>
3365 sendemail.suppressfrom
3366 </dt>
3367 <dt>
3368 sendemail.to
3369 </dt>
3370 <dt>
3371 sendemail.smtpserver
3372 </dt>
3373 <dt>
3374 sendemail.smtpserverport
3375 </dt>
3376 <dt>
3377 sendemail.smtpuser
3378 </dt>
3379 <dt>
3380 sendemail.thread
3381 </dt>
3382 <dt>
3383 sendemail.validate
3384 </dt>
3385 <dd>
3386 <p>
3388 </p>
3389 </dd>
3390 <dt>
3391 sendemail.signedoffcc
3392 </dt>
3393 <dd>
3394 <p>
3396 </p>
3397 </dd>
3398 <dt>
3399 showbranch.default
3400 </dt>
3401 <dd>
3402 <p>
3405 </p>
3406 </dd>
3407 <dt>
3408 status.relativePaths
3409 </dt>
3410 <dd>
3411 <p>
3414 relative to the repository root (this was the default for git
3415 prior to v1.5.4).
3416 </p>
3417 </dd>
3418 <dt>
3419 status.showUntrackedFiles
3420 </dt>
3421 <dd>
3422 <p>
3423 By default, <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a> show
3424 files which are not currently tracked by Git. Directories which
3425 contain only untracked files, are shown with the directory name
3426 only. Showing untracked files means that Git needs to lstat() all
3427 all the files in the whole repository, which might be slow on some
3428 systems. So, this variable controls how the commands displays
3429 the untracked files. Possible values are:
3430 </p>
3432 <li>
3433 <p>
3435 </p>
3436 </li>
3437 <li>
3438 <p>
3440 </p>
3441 </li>
3442 <li>
3443 <p>
3445 </p>
3446 </li>
3447 </ul></div>
3449 This variable can be overridden with the -u|--untracked-files option
3450 of <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a>.</p></div>
3451 </dd>
3452 <dt>
3453 tar.umask
3454 </dt>
3455 <dd>
3456 <p>
3457 This variable can be used to restrict the permission bits of
3458 tar archive entries. The default is 0002, which turns off the
3459 world write bit. The special value "user" indicates that the
3460 archiving user's umask will be used instead. See umask(2) and
3462 </p>
3463 </dd>
3464 <dt>
3465 transfer.unpackLimit
3466 </dt>
3467 <dd>
3468 <p>
3470 not set, the value of this variable is used instead.
3471 The default value is 100.
3472 </p>
3473 </dd>
3474 <dt>
3476 </dt>
3477 <dd>
3478 <p>
3479 Any URL that starts with this value will be rewritten to
3481 large number of repositories, and serves them with multiple
3482 access methods, and some users need to use different access
3483 methods, this feature allows people to specify any of the
3484 equivalent URLs and have git automatically rewrite the URL to
3485 the best alternative for the particular user, even for a
3486 never-before-seen repository on the site. When more than one
3487 insteadOf strings match a given URL, the longest match is used.
3488 </p>
3489 </dd>
3490 <dt>
3492 </dt>
3493 <dd>
3494 <p>
3495 Any URL that starts with this value will not be pushed to;
3497 resulting URL will be pushed to. In cases where some site serves
3498 a large number of repositories, and serves them with multiple
3499 access methods, some of which do not allow push, this feature
3500 allows people to specify a pull-only URL and have git
3501 automatically use an appropriate URL to push, even for a
3502 never-before-seen repository on the site. When more than one
3503 pushInsteadOf strings match a given URL, the longest match is
3504 used. If a remote has an explicit pushurl, git will ignore this
3505 setting for that remote.
3506 </p>
3507 </dd>
3508 <dt>
3509 user.email
3510 </dt>
3511 <dd>
3512 <p>
3513 Your email address to be recorded in any newly created commits.
3515 <em>EMAIL</em> environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.
3516 </p>
3517 </dd>
3518 <dt>
3519 user.name
3520 </dt>
3521 <dd>
3522 <p>
3523 Your full name to be recorded in any newly created commits.
3526 </p>
3527 </dd>
3528 <dt>
3529 user.signingkey
3530 </dt>
3531 <dd>
3532 <p>
3534 automatically when creating a signed tag, you can override the
3535 default selection with this variable. This option is passed
3536 unchanged to gpg's --local-user parameter, so you may specify a key
3537 using any method that gpg supports.
3538 </p>
3539 </dd>
3540 <dt>
3541 web.browser
3542 </dt>
3543 <dd>
3544 <p>
3545 Specify a web browser that may be used by some commands.
3546 Currently only <a href="git-instaweb.html">git-instaweb(1)</a> and <a href="git-help.html">git-help(1)</a>
3547 may use it.
3548 </p>
3549 </dd>
3550 </dl></div>
3551 </div>
3554 <div class="para"><p>Written by Johannes Schindelin <Johannes.Schindelin@gmx.de></p></div>
3555 </div>
3558 <div class="para"><p>Documentation by Johannes Schindelin, Petr Baudis and the git-list <git@vger.kernel.org>.</p></div>
3559 </div>
3563 </div>
3567 </div>
3568 </div>
3569 </body>
3570 </html>