X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=git-repo-config.html;h=e306688c96aa995f399d80bbf2551d555e2d5684;hb=f1d1480d8b938444a1617692e3f7df6d8e4cc911;hp=66606be35c908fe5b6fd7f58f9f1e71b7fd680db;hpb=88a3a070894a23a10133fee89065cb27199cf58b;p=git.git diff --git a/git-repo-config.html b/git-repo-config.html index 66606be3..e306688c 100644 --- a/git-repo-config.html +++ b/git-repo-config.html @@ -286,25 +286,26 @@ git-repo-config(1) Manual Page

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.

-

If you want to set/unset an option which can occur on multiple lines, you -should provide a POSIX regex for the value. If you want to handle the lines -not matching the regex, just prepend a single exclamation mark in front -(see EXAMPLES).

+

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 not match the regex, just +prepend a single exclamation mark in front (see EXAMPLES).

The type specifier can be either --int or --bool, which will make git-repo-config 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.

-

This command will fail if

+

This command will fail if:

  1. -.git/config is invalid, +The .git/config file is invalid,

  2. -.git/config can not be written to, +Can not write to .git/config,

  3. @@ -337,7 +338,7 @@ you try to unset/set an option for which multiple lines match.

    - Default behaviour is to replace at most one line. This replaces + Default behavior is to replace at most one line. This replaces all lines matching the key (and optionally the value_regex).

    @@ -488,14 +489,14 @@ i.e. the one without a "for …" postfix, do something like this:

    CONFIGURATION FILE

    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 +the git command's behavior. They can be used by both the git plumbing +and the porcelains. The variables are divided into 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.

    The syntax is fairly flexible and permissive; whitespaces are mostly -ignored. The # and ; characters begin commends to the end of line, +ignored. The # and ; characters begin comments 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 name = value. If there is no equal @@ -519,8 +520,8 @@ enclosed in double quotes; some variables may require special value format.

    Variables

    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 +For command-specific variables, you will find a more detailed description +in the appropriate manual page. You will find a description of non-core porcelain configuration variables in the respective porcelain documentation.

    @@ -546,12 +547,9 @@ core.gitProxy may be set multiple times and is matched in the given order; the first match wins.

    -
    -
    -
    Can be overriden by the 'GIT_PROXY_COMMAND' environment variable
+
    Can be overridden by the GIT_PROXY_COMMAND environment variable
 (which always applies universally, without the special "for"
-handling).
    -
    +handling).

    core.ignoreStat @@ -577,6 +575,19 @@ core.preferSymlinkRefs

    +core.logAllRefUpdates +
    +
    +

    + If true, git-update-ref will append a line to + "$GIT_DIR/logs/<ref>" listing the new SHA1 and the date/time + of the update. If the file does not exist it will be + created automatically. This information can be used to + determine what commit was the tip of a branch "2 days ago". + This value is false by default (no logging). +

    +
    +
    core.repositoryFormatVersion
    @@ -605,6 +616,20 @@ core.warnAmbiguousRefs

    +alias.* +
    +
    +

    + Command aliases for the git(1) command wrapper - e.g. + after defining "alias.last = cat-file commit HEAD", the invocation + "git last" is equivalent to "git cat-file commit HEAD". To avoid + confusion and troubles with script usage, aliases that + hide existing git commands are ignored. Arguments are split by + spaces, the usual shell quoting and escaping is supported. + quote pair and a backslash can be used to quote them. +

    +
    +
    apply.whitespace
    @@ -655,7 +680,7 @@ http.sslVerify

    Whether to verify the SSL certificate when fetching or pushing - over HTTPS. Can be overriden by the GIT_SSL_NO_VERIFY environment + over HTTPS. Can be overridden by the GIT_SSL_NO_VERIFY environment variable.

    @@ -665,7 +690,7 @@ http.sslCert

    File containing the SSL certificate when fetching or pushing - over HTTPS. Can be overriden by the GIT_SSL_CERT environment + over HTTPS. Can be overridden by the GIT_SSL_CERT environment variable.

    @@ -675,7 +700,7 @@ http.sslKey

    File containing the SSL private key when fetching or pushing - over HTTPS. Can be overriden by the GIT_SSL_KEY environment + over HTTPS. Can be overridden by the GIT_SSL_KEY environment variable.

    @@ -685,7 +710,7 @@ http.sslCAInfo

    File containing the certificates to verify the peer with when - fetching or pushing over HTTPS. Can be overriden by the + fetching or pushing over HTTPS. Can be overridden by the GIT_SSL_CAINFO environment variable.

    @@ -695,7 +720,7 @@ http.sslCAPath

    Path containing files with the CA certificates to verify the peer - with when fetching or pushing over HTTPS. Can be overriden + with when fetching or pushing over HTTPS. Can be overridden by the GIT_SSL_CAPATH environment variable.

    @@ -704,7 +729,7 @@ http.maxRequests

    - How many HTTP requests to launch in parallel. Can be overriden + How many HTTP requests to launch in parallel. Can be overridden by the GIT_HTTP_MAX_REQUESTS environment variable. Default is 5.

    @@ -715,7 +740,7 @@ http.lowSpeedLimit, http.lowSpeedTime

    If the HTTP transfer speed is less than http.lowSpeedLimit for longer than http.lowSpeedTime seconds, the transfer is aborted. - Can be overriden by the GIT_HTTP_LOW_SPEED_LIMIT and + Can be overridden by the GIT_HTTP_LOW_SPEED_LIMIT and GIT_HTTP_LOW_SPEED_TIME environment variables.

    @@ -781,7 +806,7 @@ user.email

    Your email address to be recorded in any newly created commits. - Can be overriden by the GIT_AUTHOR_EMAIL and GIT_COMMITTER_EMAIL + Can be overridden by the GIT_AUTHOR_EMAIL and GIT_COMMITTER_EMAIL environment variables. See git-commit-tree(1).

    @@ -791,7 +816,7 @@ user.name

    Your full name to be recorded in any newly created commits. - Can be overriden by the GIT_AUTHOR_NAME and GIT_COMMITTER_NAME + Can be overridden by the GIT_AUTHOR_NAME and GIT_COMMITTER_NAME environment variables. See git-commit-tree(1).

    @@ -829,7 +854,7 @@ imap