Differences

This shows you the differences between two versions of the page.

--- git_config [2019/02/18 09:42] – [.git/config (--local)] rpjday
+++ git_config [2019/02/18 09:57] (current) – [Configuration sections and keys] rpjday
@@ Line 96: / Line 96: @@
 ==== ~/.gitconfig (--global) ====
-Per-user (it would have killed them to call it ''%%--%%user''?):
+Per-user:
 <code>
@@ Line 137: / Line 137: @@
 NOTE: If you don't specify which of the three levels you want, the operation defaults to ''%%--%%local'', which will fail if you are not inside a working tree, and is probably not what you want, anyway.
-===== Setting your configuration =====
-==== Global configuration ====
-Setting globally (in personal ''~/.gitconfig''):
-<code>
-$ git config --global user.name "Robert P. J. Day"
-$ git config --global user.email "rpjday@crashcourse.ca"
-$ git config --global color.ui false
-</code>
-==== Local configuration ====
-Setting locally (in repo's ''.git/config''):
-<code>
-$ git config [--local] gui.wmstate normal   (the default mode)
-</code>
 ===== Listing config settings =====
@@ Line 207: / Line 187: @@
 ===== Overriding configuration settings =====
-==== One-time config override with -c ====
-<code>
-$ git -c user.name="Keyser Soze" <command>...
-</code>
 ==== Environment variables ====
-As an example, ''git commit'' searches for the editor to use when entering the commit message:
+Most Git commands support environment variables for overriding configuration settings. As an example, ''git commit'' searches for the editor to use when entering the commit message:
   * ''GIT_EDITOR'' environment variable
@@ Line 234: / Line 210: @@
 </code>
-===== Configuration sections and keys =====
+==== One-time config override with -c ====
+If you need a one-time-only override of some config setting, most Git commands support the "-c" option:
+<code>
+$ git -c user.name="Keyser Soze" <some command>...
+</code>
+===== Sections and subsections =====
 Format of ''<section>.<key>'':