The name is actually the section and the key separated by a dot, 60 seconds binary option tutorial strategies the value will be escaped. Multiple lines can be added to an option by using the –add option.

If you want to update or 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 no type specifier is passed, no checks or transformations are performed on the value. On success, the command returns the exit code 0. Adds a new line to the option without altering any existing values. Like get, but returns all values for a multi-valued key.

Like –get-all, but interprets the name as a regular expression and writes out the key names. Regular expression matching is currently case-sensitive and done against a canonicalized version of the key in which section and variable names are lowercased, but subsection names are not. When given just the section as name, do so for all the keys in the section and list them. For writing options: write to the repository .

For reading options: read only from the repository . Use the given config file instead of the one specified by GIT_CONFIG. Similar to –file but use the given blob instead of a file. See “SPECIFYING REVISIONS” section in gitrevisions for a more complete list of ways to spell blob names.

Remove the given section from the configuration file. Rename the given section to a new name. Remove the line matching the key from config file. Remove all lines matching the key from config file. List all variables set in config file, along with their values.

An optional value suffix of k, m, or g in the config file will cause the value to be multiplied by 1024, 1048576, or 1073741824 prior to output. This option has no effect when setting the value. Use newline instead as a delimiter between key and value. This allows for secure parsing of the output without getting confused e. Output only the names of config variables for –list or –get-regexp. ANSI color escape sequence to the standard output.

The optional default parameter is used instead, if there is no color configured for name. The default is to use a pager. If no further options are given, all reading options will read all of these files that are available. If the global or the system-wide configuration file are not available they will be ignored. The files are read in the order given above, with last value found taking precedence over values read earlier. When multiple values are taken then all values of a key from all files will be used. You may override individual configuration parameters when running any git command by using the -c option.