</p>\r
</dd>\r
<dt>\r
+--origin <name>\r
+</dt>\r
+<dt>\r
-o <name>\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 03-Oct-2006 08:40:56 UTC\r
+Last updated 03-Nov-2006 02:39:57 UTC\r
</div>\r
</div>\r
</body>\r
this option is used, neither the `origin` branch nor the
default `remotes/origin` file is created.
+--origin <name>::
-o <name>::
Instead of using the branch name 'origin' to keep track
of the upstream repository, use <name> instead. Note
</div></div>\r
<p>For example, let's say that you have worked on your working directory, updated\r
some files in the index and are ready to commit. You want to see exactly\r
-<strong>what</strong> you are going to commit is without having to write a new tree\r
+<strong>what</strong> you are going to commit, without having to write a new tree\r
object and compare it that way, and to do that, you just do</p>\r
<div class="literalblock">\r
<div class="content">\r
-100644 blob 4161aecc6700a2eb579e842af0b7f22b98443f74 commit.c\r
+100644 blob 4161aecc6700a2eb579e842af0b7f22b98443f74 git-commit.c</tt></pre>\r
</div></div>\r
-<p>You can trivially see that the above is a rename.</p>\r
+<p>You can see easily that the above is a rename.</p>\r
<p>In fact, "git-diff-index --cached" <strong>should</strong> always be entirely equivalent to\r
actually doing a "git-write-tree" and comparing that. Except this one is much\r
nicer for the case where you just want to check where you are.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 27-Oct-2006 09:29:00 UTC\r
+Last updated 03-Nov-2006 02:39:57 UTC\r
</div>\r
</div>\r
</body>\r
For example, let's say that you have worked on your working directory, updated
some files in the index and are ready to commit. You want to see exactly
-*what* you are going to commit is without having to write a new tree
+*what* you are going to commit, without having to write a new tree
object and compare it that way, and to do that, you just do
git-diff-index --cached HEAD
-100644 blob 4161aecc6700a2eb579e842af0b7f22b98443f74 commit.c
+100644 blob 4161aecc6700a2eb579e842af0b7f22b98443f74 git-commit.c
-You can trivially see that the above is a rename.
+You can see easily that the above is a rename.
In fact, "git-diff-index --cached" *should* always be entirely equivalent to
actually doing a "git-write-tree" and comparing that. Except this one is much
<h2>NAME</h2>\r
<div class="sectionbody">\r
<p>git-repo-config -\r
- Get and set options in .git/config\r
+ Get and set repository or global options.\r
</p>\r
</div>\r
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
<div class="verseblock">\r
-<div class="content"><em>git-repo-config</em> [type] name [value [value_regex]]\r
-<em>git-repo-config</em> [type] --replace-all name [value [value_regex]]\r
-<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]\r
-<em>git-repo-config</em> -l | --list</div></div>\r
+<div class="content"><em>git-repo-config</em> [--global] [type] name [value [value_regex]]\r
+<em>git-repo-config</em> [--global] [type] --replace-all name [value [value_regex]]\r
+<em>git-repo-config</em> [--global] [type] --get name [value_regex]\r
+<em>git-repo-config</em> [--global] [type] --get-all name [value_regex]\r
+<em>git-repo-config</em> [--global] [type] --unset name [value_regex]\r
+<em>git-repo-config</em> [--global] [type] --unset-all name [value_regex]\r
+<em>git-repo-config</em> [--global] -l | --list</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
</li>\r
<li>\r
<p>\r
-you try to unset an option which does not exist, or\r
+you try to unset an option which does not exist,\r
</p>\r
</li>\r
<li>\r
<p>\r
-you try to unset/set an option for which multiple lines match.\r
+you try to unset/set an option for which multiple lines match, or\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+you use --global option without $HOME being properly set.\r
</p>\r
</li>\r
</ol>\r
</p>\r
</dd>\r
<dt>\r
+--global\r
+</dt>\r
+<dd>\r
+<p>\r
+ Use global ~/.gitconfig file rather than the repository .git/config.\r
+</p>\r
+</dd>\r
+<dt>\r
--unset\r
</dt>\r
<dd>\r
<p>\r
- Remove the line matching the key from .git/config.\r
+ Remove the line matching the key from config file.\r
</p>\r
</dd>\r
<dt>\r
</dt>\r
<dd>\r
<p>\r
- Remove all matching lines from .git/config.\r
+ Remove all matching lines from config file.\r
</p>\r
</dd>\r
<dt>\r
</dt>\r
<dd>\r
<p>\r
- List all variables set in .git/config.\r
+ List all variables set in config file.\r
</p>\r
</dd>\r
</dl>\r
<dd>\r
<p>\r
Take the configuration from the given file instead of .git/config.\r
+ Using the "--global" option forces this to ~/.gitconfig.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 02-Nov-2006 00:22:39 UTC\r
+Last updated 03-Nov-2006 02:39:58 UTC\r
</div>\r
</div>\r
</body>\r
NAME
----
-git-repo-config - Get and set options in .git/config
+git-repo-config - Get and set repository or global options.
SYNOPSIS
--------
[verse]
-'git-repo-config' [type] name [value [value_regex]]
-'git-repo-config' [type] --replace-all name [value [value_regex]]
-'git-repo-config' [type] --get name [value_regex]
-'git-repo-config' [type] --get-all name [value_regex]
-'git-repo-config' [type] --unset name [value_regex]
-'git-repo-config' [type] --unset-all name [value_regex]
-'git-repo-config' -l | --list
+'git-repo-config' [--global] [type] name [value [value_regex]]
+'git-repo-config' [--global] [type] --replace-all name [value [value_regex]]
+'git-repo-config' [--global] [type] --get name [value_regex]
+'git-repo-config' [--global] [type] --get-all name [value_regex]
+'git-repo-config' [--global] [type] --unset name [value_regex]
+'git-repo-config' [--global] [type] --unset-all name [value_regex]
+'git-repo-config' [--global] -l | --list
DESCRIPTION
-----------
. Can not write to .git/config,
. no section was provided,
. the section or key is invalid,
-. you try to unset an option which does not exist, or
-. you try to unset/set an option for which multiple lines match.
+. you try to unset an option which does not exist,
+. you try to unset/set an option for which multiple lines match, or
+. you use --global option without $HOME being properly set.
OPTIONS
--get-regexp::
Like --get-all, but interprets the name as a regular expression.
+--global::
+ Use global ~/.gitconfig file rather than the repository .git/config.
+
--unset::
- Remove the line matching the key from .git/config.
+ Remove the line matching the key from config file.
--unset-all::
- Remove all matching lines from .git/config.
+ Remove all matching lines from config file.
-l, --list::
- List all variables set in .git/config.
+ List all variables set in config file.
ENVIRONMENT
GIT_CONFIG::
Take the configuration from the given file instead of .git/config.
+ Using the "--global" option forces this to ~/.gitconfig.
GIT_CONFIG_LOCAL::
Currently the same as $GIT_CONFIG; when Git will support global