<em>git-repo-config</em> [type] --get name [value_regex]\r
<em>git-repo-config</em> [type] --get-all name [value_regex]\r
<em>git-repo-config</em> [type] --unset name [value_regex]\r
-<em>git-repo-config</em> [type] --unset-all name [value_regex]</div></div>\r
+<em>git-repo-config</em> [type] --unset-all name [value_regex]\r
+<em>git-repo-config</em> -l | --list</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
<p>You can query/set/replace/unset options with this command. The name is\r
actually the section and the key separated by a dot, and the value will be\r
escaped.</p>\r
-<p>If you want to set/unset an option which can occur on multiple lines, you\r
-should provide a POSIX regex for the value. If you want to handle the lines\r
-<strong>not</strong> matching the regex, just prepend a single exclamation mark in front\r
-(see EXAMPLES).</p>\r
+<p>If you want to set/unset an option which can occur on multiple\r
+lines, a POSIX regexp <tt>value_regex</tt> needs to be given. Only the\r
+existing values that match the regexp are updated or unset. If\r
+you want to handle the lines that do <strong>not</strong> match the regex, just\r
+prepend a single exclamation mark in front (see EXAMPLES).</p>\r
<p>The type specifier can be either <em>--int</em> or <em>--bool</em>, which will make\r
<em>git-repo-config</em> ensure that the variable(s) are of the given type and\r
convert the value to the canonical form (simple decimal number for int,\r
a "true" or "false" string for bool). If no type specifier is passed,\r
no checks or transformations are performed on the value.</p>\r
-<p>This command will fail if</p>\r
+<p>This command will fail if:</p>\r
<ol>\r
<li>\r
<p>\r
-.git/config is invalid,\r
+The .git/config file is invalid,\r
</p>\r
</li>\r
<li>\r
<p>\r
-.git/config can not be written to,\r
+Can not write to .git/config,\r
</p>\r
</li>\r
<li>\r
</dt>\r
<dd>\r
<p>\r
- Default behaviour is to replace at most one line. This replaces\r
- all lines matching the key (and optionally the value_regex)\r
+ Default behavior is to replace at most one line. This replaces\r
+ all lines matching the key (and optionally the value_regex).\r
</p>\r
</dd>\r
<dt>\r
</p>\r
</dd>\r
<dt>\r
+--get-regexp\r
+</dt>\r
+<dd>\r
+<p>\r
+ Like --get-all, but interprets the name as a regular expression.\r
+</p>\r
+</dd>\r
+<dt>\r
--unset\r
</dt>\r
<dd>\r
Remove all matching lines from .git/config.\r
</p>\r
</dd>\r
+<dt>\r
+-l, --list\r
+</dt>\r
+<dd>\r
+<p>\r
+ List all variables set in .git/config.\r
+</p>\r
+</dd>\r
</dl>\r
</div>\r
<h2>EXAMPLE</h2>\r
<h2>CONFIGURATION FILE</h2>\r
<div class="sectionbody">\r
<p>The git configuration file contains a number of variables that affect\r
-the git commands behaviour. They can be used by both the git plumbing\r
-and the porcelains. The variables are divided to sections, where\r
+the git command's behavior. They can be used by both the git plumbing\r
+and the porcelains. The variables are divided into sections, where\r
in the fully qualified variable name the variable itself is the last\r
dot-separated segment and the section name is everything before the last\r
dot. The variable names are case-insensitive and only alphanumeric\r
characters are allowed. Some variables may appear multiple times.</p>\r
<p>The syntax is fairly flexible and permissive; whitespaces are mostly\r
-ignored. The <em>#</em> and <em>;</em> characters begin commends to the end of line,\r
+ignored. The <em>#</em> and <em>;</em> characters begin comments to the end of line,\r
blank lines are ignored, lines containing strings enclosed in square\r
brackets start sections and all the other lines are recognized\r
as setting variables, in the form <em>name = value</em>. If there is no equal\r
</div></div>\r
<h3>Variables</h3>\r
<p>Note that this list is non-comprehensive and not necessarily complete.\r
-For command-specific variables, you will find more detailed description\r
-in the appropriate manual page. You will find description of non-core\r
+For command-specific variables, you will find a more detailed description\r
+in the appropriate manual page. You will find a description of non-core\r
porcelain configuration variables in the respective porcelain documentation.</p>\r
<dl>\r
<dt>\r
may be set multiple times and is matched in the given order;\r
the first match wins.\r
</p>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt>Can be overriden by the 'GIT_PROXY_COMMAND' environment variable\r
+<p>Can be overridden by the <em>GIT_PROXY_COMMAND</em> environment variable\r
(which always applies universally, without the special "for"\r
-handling).</tt></pre>\r
-</div></div>\r
+handling).</p>\r
</dd>\r
<dt>\r
core.ignoreStat\r
</p>\r
</dd>\r
<dt>\r
-core.onlyUseSymrefs\r
+core.preferSymlinkRefs\r
+</dt>\r
+<dd>\r
+<p>\r
+ Instead of the default "symref" format for HEAD\r
+ and other symbolic reference files, use symbolic links.\r
+ This is sometimes needed to work with old scripts that\r
+ expect HEAD to be a symbolic link.\r
+</p>\r
+</dd>\r
+<dt>\r
+core.logAllRefUpdates\r
</dt>\r
<dd>\r
<p>\r
- Always use the "symref" format instead of symbolic links for HEAD\r
- and other symbolic reference files. True by default.\r
+ If true, <tt>git-update-ref</tt> will append a line to\r
+ "$GIT_DIR/logs/<ref>" listing the new SHA1 and the date/time\r
+ of the update. If the file does not exist it will be\r
+ created automatically. This information can be used to\r
+ determine what commit was the tip of a branch "2 days ago".\r
+ This value is false by default (no logging).\r
</p>\r
</dd>\r
<dt>\r
</p>\r
</dd>\r
<dt>\r
+alias.*\r
+</dt>\r
+<dd>\r
+<p>\r
+ Command aliases for the <a href="git.html">git(1)</a> command wrapper - e.g.\r
+ after defining "alias.last = cat-file commit HEAD", the invocation\r
+ "git last" is equivalent to "git cat-file commit HEAD". To avoid\r
+ confusion and troubles with script usage, aliases that\r
+ hide existing git commands are ignored. Arguments are split by\r
+ spaces, the usual shell quoting and escaping is supported.\r
+ quote pair and a backslash can be used to quote them.\r
+</p>\r
+</dd>\r
+<dt>\r
apply.whitespace\r
</dt>\r
<dd>\r
<dd>\r
<p>\r
Whether to verify the SSL certificate when fetching or pushing\r
- over HTTPS. Can be overriden by the <em>GIT_SSL_NO_VERIFY</em> environment\r
+ over HTTPS. Can be overridden by the <em>GIT_SSL_NO_VERIFY</em> environment\r
variable.\r
</p>\r
</dd>\r
<dd>\r
<p>\r
File containing the SSL certificate when fetching or pushing\r
- over HTTPS. Can be overriden by the <em>GIT_SSL_CERT</em> environment\r
+ over HTTPS. Can be overridden by the <em>GIT_SSL_CERT</em> environment\r
variable.\r
</p>\r
</dd>\r
<dd>\r
<p>\r
File containing the SSL private key when fetching or pushing\r
- over HTTPS. Can be overriden by the <em>GIT_SSL_KEY</em> environment\r
+ over HTTPS. Can be overridden by the <em>GIT_SSL_KEY</em> environment\r
variable.\r
</p>\r
</dd>\r
<dd>\r
<p>\r
File containing the certificates to verify the peer with when\r
- fetching or pushing over HTTPS. Can be overriden by the\r
+ fetching or pushing over HTTPS. Can be overridden by the\r
<em>GIT_SSL_CAINFO</em> environment variable.\r
</p>\r
</dd>\r
<dd>\r
<p>\r
Path containing files with the CA certificates to verify the peer\r
- with when fetching or pushing over HTTPS. Can be overriden\r
+ with when fetching or pushing over HTTPS. Can be overridden\r
by the <em>GIT_SSL_CAPATH</em> environment variable.\r
</p>\r
</dd>\r
</dt>\r
<dd>\r
<p>\r
- How many HTTP requests to launch in parallel. Can be overriden\r
+ How many HTTP requests to launch in parallel. Can be overridden\r
by the <em>GIT_HTTP_MAX_REQUESTS</em> environment variable. Default is 5.\r
</p>\r
</dd>\r
<p>\r
If the HTTP transfer speed is less than <em>http.lowSpeedLimit</em>\r
for longer than <em>http.lowSpeedTime</em> seconds, the transfer is aborted.\r
- Can be overriden by the <em>GIT_HTTP_LOW_SPEED_LIMIT</em> and\r
+ Can be overridden by the <em>GIT_HTTP_LOW_SPEED_LIMIT</em> and\r
<em>GIT_HTTP_LOW_SPEED_TIME</em> environment variables.\r
</p>\r
</dd>\r
<dd>\r
<p>\r
Your email address to be recorded in any newly created commits.\r
- Can be overriden by the <em>GIT_AUTHOR_EMAIL</em> and <em>GIT_COMMITTER_EMAIL</em>\r
+ Can be overridden by the <em>GIT_AUTHOR_EMAIL</em> and <em>GIT_COMMITTER_EMAIL</em>\r
environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.\r
</p>\r
</dd>\r
<dd>\r
<p>\r
Your full name to be recorded in any newly created commits.\r
- Can be overriden by the <em>GIT_AUTHOR_NAME</em> and <em>GIT_COMMITTER_NAME</em>\r
+ Can be overridden by the <em>GIT_AUTHOR_NAME</em> and <em>GIT_COMMITTER_NAME</em>\r
environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.\r
</p>\r
</dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 25-Apr-2006 07:36:44 UTC\r
+Last updated 08-Jun-2006 00:48:14 UTC\r
</div>\r
</div>\r
</body>\r
projects / git.git / blobdiff