1 .\"Generated by db2man.xsl. Don't modify this, modify the source.
10 .de Sp \" Vertical space (when we can't use .PP)
16 .ie \\n(.$>=3 .ne \\$3
20 .TH "GIT-REPO-CONFIG" 1 "" "" ""
22 git-repo-config \- Get and set options in .git/config
26 \fIgit\-repo\-config\fR [type] name [value [value_regex]]
27 \fIgit\-repo\-config\fR [type] \-\-replace\-all name [value [value_regex]]
28 \fIgit\-repo\-config\fR [type] \-\-get name [value_regex]
29 \fIgit\-repo\-config\fR [type] \-\-get\-all name [value_regex]
30 \fIgit\-repo\-config\fR [type] \-\-unset name [value_regex]
31 \fIgit\-repo\-config\fR [type] \-\-unset\-all name [value_regex]
32 \fIgit\-repo\-config\fR \-l | \-\-list
38 You can query/set/replace/unset options with this command\&. The name is actually the section and the key separated by a dot, and the value will be escaped\&.
41 If you want to set/unset an option which can occur on multiple lines, a POSIX regexp value_regex needs to be given\&. Only the existing values that match the regexp are updated or unset\&. If you want to handle the lines that do \fInot\fR match the regex, just prepend a single exclamation mark in front (see EXAMPLES)\&.
44 The type specifier can be either \fI\-\-int\fR or \fI\-\-bool\fR, which will make \fIgit\-repo\-config\fR ensure that the variable(s) are of the given type and convert the value to the canonical form (simple decimal number for int, a "true" or "false" string for bool)\&. If no type specifier is passed, no checks or transformations are performed on the value\&.
47 This command will fail if:
51 The \&.git/config file is invalid,
54 Can not write to \&.git/config,
57 no section was provided,
60 the section or key is invalid,
63 you try to unset an option which does not exist, or
66 you try to unset/set an option for which multiple lines match\&.
73 Default behaviour is to replace at most one line\&. This replaces all lines matching the key (and optionally the value_regex)\&.
77 Get the value for a given key (optionally filtered by a regex matching the value)\&.
81 Like get, but does not fail if the number of values for the key is not exactly one\&.
85 Like \-\-get\-all, but interprets the name as a regular expression\&.
89 Remove the line matching the key from \&.git/config\&.
93 Remove all matching lines from \&.git/config\&.
97 List all variables set in \&.git/config\&.
102 Given a \&.git/config like this:
106 # This is the config file, and
107 # a '#' or ';' character indicates
115 ; Don't trust file modes
122 external = "/usr/local/bin/gnu\-diff \-u"
129 gitproxy="ssh" for "ssh://kernel\&.org/"
130 gitproxy="proxy\-command" for kernel\&.org
131 gitproxy="myprotocol\-command" for "my://"
132 gitproxy=default\-proxy ; for all the rest
136 you can set the filemode to true with
139 % git repo\-config core\&.filemode true
143 The hypothetic proxy command entries actually have a postfix to discern to what URL they apply\&. Here is how to change the entry for kernel\&.org to "ssh"\&.
146 % git repo\-config core\&.gitproxy '"ssh" for kernel\&.org' 'for kernel\&.org$'
150 This makes sure that only the key/value pair for kernel\&.org is replaced\&.
153 To delete the entry for renames, do
156 % git repo\-config \-\-unset diff\&.renames
160 If you want to delete an entry for a multivar (like core\&.gitproxy above), you have to provide a regex matching the value of exactly one line\&.
163 To query the value for a given key, do
166 % git repo\-config \-\-get core\&.filemode
173 % git repo\-config core\&.filemode
177 or, to query a multivar:
180 % git repo\-config \-\-get core\&.gitproxy "for kernel\&.org$"
184 If you want to know all the values for a multivar, do:
187 % git repo\-config \-\-get\-all core\&.gitproxy
191 If you like to live dangerous, you can replace \fIall\fR core\&.gitproxy by a new one with
194 % git repo\-config \-\-replace\-all core\&.gitproxy ssh
198 However, if you really only want to replace the line for the default proxy, i\&.e\&. the one without a "for ..." postfix, do something like this:
201 % git repo\-config core\&.gitproxy ssh '! for '
205 To actually match only values with an exclamation mark, you have to
208 % git repo\-config section\&.key value '[!]'
211 .SH "CONFIGURATION FILE"
214 The git configuration file contains a number of variables that affect the git commands behaviour\&. They can be used by both the git plumbing and the porcelains\&. The variables are divided to sections, where in the fully qualified variable name the variable itself is the last dot\-separated segment and the section name is everything before the last dot\&. The variable names are case\-insensitive and only alphanumeric characters are allowed\&. Some variables may appear multiple times\&.
217 The syntax is fairly flexible and permissive; whitespaces are mostly ignored\&. The \fI#\fR and \fI;\fR characters begin commends to the end of line, blank lines are ignored, lines containing strings enclosed in square brackets start sections and all the other lines are recognized as setting variables, in the form \fIname = value\fR\&. If there is no equal sign on the line, the entire line is taken as \fIname\fR and the variable is recognized as boolean "true"\&. String values may be entirely or partially enclosed in double quotes; some variables may require special value format\&.
224 ; Don't trust file modes
231 external = "/usr/local/bin/gnu\-diff \-u"
238 Note that this list is non\-comprehensive and not necessarily complete\&. For command\-specific variables, you will find more detailed description in the appropriate manual page\&. You will find description of non\-core porcelain configuration variables in the respective porcelain documentation\&.
242 If false, the executable bit differences between the index and the working copy are ignored; useful on broken filesystems like FAT\&. See \fBgit\-update\-index\fR(1)\&. True by default\&.
246 A "proxy command" to execute (as \fIcommand host port\fR) instead of establishing direct connection to the remote server when using the git protocol for fetching\&. If the variable value is in the "COMMAND for DOMAIN" format, the command is applied only on hostnames ending with the specified domain string\&. This variable may be set multiple times and is matched in the given order; the first match wins\&.
249 Can be overriden by the 'GIT_PROXY_COMMAND' environment variable
250 (which always applies universally, without the special "for"
256 The working copy files are assumed to stay unchanged until you mark them otherwise manually \- Git will not detect the file changes by lstat() calls\&. This is useful on systems where those are very slow, such as Microsoft Windows\&. See \fBgit\-update\-index\fR(1)\&. False by default\&.
259 core\&.preferSymlinkRefs
260 Instead of the default "symref" format for HEAD and other symbolic reference files, use symbolic links\&. This is sometimes needed to work with old scripts that expect HEAD to be a symbolic link\&.
263 core\&.repositoryFormatVersion
264 Internal variable identifying the repository format and layout version\&.
267 core\&.sharedRepository
268 If true, the repository is made shareable between several users in a group (making sure all the files and objects are group\-writable)\&. See \fBgit\-init\-db\fR(1)\&. False by default\&.
271 core\&.warnAmbiguousRefs
272 If true, git will warn you if the ref name you passed it is ambiguous and might match multiple refs in the \&.git/refs/ tree\&. True by default\&.
276 Tells git\-apply how to handle whitespaces, in the same way as the \fI\-\-whitespace\fR option\&. See \fBgit\-apply\fR(1)\&.
280 The number of files to consider when performing the copy/rename detection; equivalent to the git diff option \fI\-l\fR\&.
284 Additional email headers to include in a patch to be submitted by mail\&. See \fBgit\-format\-patch\fR(1)\&.
288 Whether the cvs pserver interface is enabled for this repository\&. See \fBgit\-cvsserver\fR(1)\&.
292 Path to a log file where the cvs pserver interface well... logs various stuff\&. See \fBgit\-cvsserver\fR(1)\&.
296 Whether to verify the SSL certificate when fetching or pushing over HTTPS\&. Can be overriden by the \fIGIT_SSL_NO_VERIFY\fR environment variable\&.
300 File containing the SSL certificate when fetching or pushing over HTTPS\&. Can be overriden by the \fIGIT_SSL_CERT\fR environment variable\&.
304 File containing the SSL private key when fetching or pushing over HTTPS\&. Can be overriden by the \fIGIT_SSL_KEY\fR environment variable\&.
308 File containing the certificates to verify the peer with when fetching or pushing over HTTPS\&. Can be overriden by the \fIGIT_SSL_CAINFO\fR environment variable\&.
312 Path containing files with the CA certificates to verify the peer with when fetching or pushing over HTTPS\&. Can be overriden by the \fIGIT_SSL_CAPATH\fR environment variable\&.
316 How many HTTP requests to launch in parallel\&. Can be overriden by the \fIGIT_HTTP_MAX_REQUESTS\fR environment variable\&. Default is 5\&.
319 http\&.lowSpeedLimit, http\&.lowSpeedTime
320 If the HTTP transfer speed is less than \fIhttp\&.lowSpeedLimit\fR for longer than \fIhttp\&.lowSpeedTime\fR seconds, the transfer is aborted\&. Can be overriden by the \fIGIT_HTTP_LOW_SPEED_LIMIT\fR and \fIGIT_HTTP_LOW_SPEED_TIME\fR environment variables\&.
323 i18n\&.commitEncoding
324 Character encoding the commit messages are stored in; git itself does not care per se, but this information is necessary e\&.g\&. when importing commits from emails or in the gitk graphical history browser (and possibly at other places in the future or in other porcelains)\&. See e\&.g\&. \fBgit\-mailinfo\fR(1)\&. Defaults to \fIutf\-8\fR\&.
328 Whether to include summaries of merged commits in newly created merge commit messages\&. False by default\&.
332 The default merge strategy to use when pulling multiple branches at once\&.
336 The default merge strategy to use when pulling a single branch\&.
340 The default \fBgit\-diff\-tree\fR(1) arguments to be used for \fBgit\-show\fR(1)\&.
344 The default set of branches for \fBgit\-show\-branch\fR(1)\&. See \fBgit\-show\-branch\fR(1)\&.
348 Your email address to be recorded in any newly created commits\&. Can be overriden by the \fIGIT_AUTHOR_EMAIL\fR and \fIGIT_COMMITTER_EMAIL\fR environment variables\&. See \fBgit\-commit\-tree\fR(1)\&.
352 Your full name to be recorded in any newly created commits\&. Can be overriden by the \fIGIT_AUTHOR_NAME\fR and \fIGIT_COMMITTER_NAME\fR environment variables\&. See \fBgit\-commit\-tree\fR(1)\&.
355 whatchanged\&.difftree
356 The default \fBgit\-diff\-tree\fR(1) arguments to be used for \fBgit\-whatchanged\fR(1)\&.
360 The configuration variables in the \fIimap\fR section are described in \fBgit\-imap\-send\fR(1)\&.
365 Written by Johannes Schindelin <Johannes\&.Schindelin@gmx\&.de>
370 Documentation by Johannes Schindelin, Petr Baudis and the git\-list <git@vger\&.kernel\&.org>\&.
375 Part of the \fBgit\fR(7) suite