format.numbered::
A boolean which can enable sequence numbers in patch subjects.
- Seting this option to "auto" will enable it only if there is
+ Setting this option to "auto" will enable it only if there is
more than one patch. See --numbered option in
gitlink:git-format-patch[1].
<dd>\r
<p>\r
A boolean which can enable sequence numbers in patch subjects.\r
- Seting this option to "auto" will enable it only if there is\r
+ Setting this option to "auto" will enable it only if there is\r
more than one patch. See --numbered option in\r
<a href="git-format-patch.html">git-format-patch(1)</a>.\r
</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 18-Dec-2007 06:59:36 UTC\r
+Last updated 19-Dec-2007 07:33:00 UTC\r
</div>\r
</div>\r
</body>\r
printed on the standard output.</p>\r
<p>If a git command is named, a manual page for that command is brought\r
up. The <em>man</em> program is used by default for this purpose, but this\r
-can be overriden by other options or configuration variables.</p>\r
+can be overridden by other options or configuration variables.</p>\r
<p>Note that <em>git --help …</em> is identical as <em>git help …</em> because the\r
former is internally converted into the latter.</p>\r
</div>\r
<dd>\r
<p>\r
Prints all the available commands on the standard output. This\r
- option superseeds any other option.\r
+ option supersedes any other option.\r
</p>\r
</dd>\r
<dt>\r
<em>help.browser</em>, or <em>web.browser</em> if the former is not set. If none of\r
these config variables is set, the <em>git-help--browse</em> helper script\r
(called by <em>git-help</em>) will pick a suitable default.</p>\r
-<p>You can explicitly provide a full path to your prefered browser by\r
+<p>You can explicitly provide a full path to your preferred browser by\r
setting the configuration variable <em>browser.<tool>.path</em>. For example,\r
you can configure the absolute path to firefox by setting\r
<em>browser.firefox.path</em>. Otherwise, <em>git-help--browse</em> assumes the tool\r
</li>\r
</ul>\r
<p>The <em>help.browser</em>, <em>web.browser</em> and <em>browser.<tool>.path</em> will also\r
-be checked if the <em>web</em> format is choosen (either by command line\r
+be checked if the <em>web</em> format is chosen (either by command line\r
option or configuration variable). See <em>-w|--web</em> in the OPTIONS\r
section above.</p>\r
<p>Note that these configuration variables should probably be set using\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Dec-2007 22:13:21 UTC\r
+Last updated 19-Dec-2007 07:33:00 UTC\r
</div>\r
</div>\r
</body>\r
If a git command is named, a manual page for that command is brought
up. The 'man' program is used by default for this purpose, but this
-can be overriden by other options or configuration variables.
+can be overridden by other options or configuration variables.
Note that 'git --help ...' is identical as 'git help ...' because the
former is internally converted into the latter.
-------
-a|--all::
Prints all the available commands on the standard output. This
- option superseeds any other option.
+ option supersedes any other option.
-i|--info::
Use the 'info' program to display the manual page, instead of
these config variables is set, the 'git-help--browse' helper script
(called by 'git-help') will pick a suitable default.
+
-You can explicitly provide a full path to your prefered browser by
+You can explicitly provide a full path to your preferred browser by
setting the configuration variable 'browser.<tool>.path'. For example,
you can configure the absolute path to firefox by setting
'browser.firefox.path'. Otherwise, 'git-help--browse' assumes the tool
* "web" or "html" correspond to '-w|--web',
The 'help.browser', 'web.browser' and 'browser.<tool>.path' will also
-be checked if the 'web' format is choosen (either by command line
+be checked if the 'web' format is chosen (either by command line
option or configuration variable). See '-w|--web' in the OPTIONS
section above.
<em>all</em> (or <em>world</em> or <em>everybody</em>): Same as <em>group</em>, but make the repository\r
readable by all users.\r
</p>\r
-<p>By default, the configuration flag receive.denyNonFastforward is enabled\r
+<p>By default, the configuration flag receive.denyNonFastForwards is enabled\r
in shared repositories, so that you cannot force a non fast-forwarding push\r
into it.</p>\r
</li>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 14-Nov-2007 12:11:34 UTC\r
+Last updated 19-Dec-2007 07:33:00 UTC\r
</div>\r
</div>\r
</body>\r
- 'all' (or 'world' or 'everybody'): Same as 'group', but make the repository
readable by all users.
-By default, the configuration flag receive.denyNonFastforward is enabled
+By default, the configuration flag receive.denyNonFastForwards is enabled
in shared repositories, so that you cannot force a non fast-forwarding push
into it.
<dd>\r
<p>\r
Don't print anything to standard output. This form of\r
- git-rev-list is primarly meant to allow the caller to\r
+ git-rev-list is primarily meant to allow the caller to\r
test the exit status to see if a range of objects is fully\r
connected (or not). It is faster than redirecting stdout\r
to /dev/null as the output does not have to be formatted.\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 15-Nov-2007 00:12:55 UTC\r
+Last updated 19-Dec-2007 07:33:01 UTC\r
</div>\r
</div>\r
</body>\r
--quiet::
Don't print anything to standard output. This form of
- git-rev-list is primarly meant to allow the caller to
+ git-rev-list is primarily meant to allow the caller to
test the exit status to see if a range of objects is fully
connected (or not). It is faster than redirecting stdout
to /dev/null as the output does not have to be formatted.
<em>sendemail.<identity>.<item></em> will have higher precedence than\r
<em>sendemail.<item></em>. This is useful to declare multiple SMTP\r
identities and to hoist sensitive authentication information\r
- out of the repository and into the global configuation file.\r
+ out of the repository and into the global configuration file.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 14-Nov-2007 12:11:47 UTC\r
+Last updated 19-Dec-2007 07:33:02 UTC\r
</div>\r
</div>\r
</body>\r
'sendemail.<identity>.<item>' will have higher precedence than
'sendemail.<item>'. This is useful to declare multiple SMTP
identities and to hoist sensitive authentication information
- out of the repository and into the global configuation file.
+ out of the repository and into the global configuration file.
sendemail.aliasesfile::
To avoid typing long email addresses, point this to one or more
as tags and branch heads.</p>\r
<p>The object database contains objects of three main types: blobs, which\r
hold file data; trees, which point to blobs and other trees to build up\r
-directory heirarchies; and commits, which each reference a single tree\r
+directory hierarchies; and commits, which each reference a single tree\r
and some number of parent commits.</p>\r
<p>The commit, equivalent to what other systems call a "changeset" or\r
"version", represents a step in the project's history, and each parent\r
<p>Named pointers called refs mark interesting points in history. A ref\r
may contain the SHA1 name of an object or the name of another ref. Refs\r
with names beginning <tt>ref/head/</tt> contain the SHA1 name of the most\r
-recent commit (or "head") of a branch under developement. SHA1 names of\r
+recent commit (or "head") of a branch under development. SHA1 names of\r
tags of interest are stored under <tt>ref/tags/</tt>. A special ref named\r
<tt>HEAD</tt> contains the name of the currently checked-out branch.</p>\r
<p>The index file is initialized with a list of all paths and, for each\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 15-Dec-2007 08:39:57 UTC\r
+Last updated 19-Dec-2007 07:33:03 UTC\r
</div>\r
</div>\r
</body>\r
The object database contains objects of three main types: blobs, which
hold file data; trees, which point to blobs and other trees to build up
-directory heirarchies; and commits, which each reference a single tree
+directory hierarchies; and commits, which each reference a single tree
and some number of parent commits.
The commit, equivalent to what other systems call a "changeset" or
Named pointers called refs mark interesting points in history. A ref
may contain the SHA1 name of an object or the name of another ref. Refs
with names beginning `ref/head/` contain the SHA1 name of the most
-recent commit (or "head") of a branch under developement. SHA1 names of
+recent commit (or "head") of a branch under development. SHA1 names of
tags of interest are stored under `ref/tags/`. A special ref named
`HEAD` contains the name of the currently checked-out branch.