machine where the repository is hosted. If you don't want to give them a\r
full shell on the machine, there is a restricted shell which only allows\r
users to do git pushes and pulls; see <a href="git-shell.html">git-shell(1)</a>.</p>\r
-<p>Put all the committers should in the same group, and make the repository\r
+<p>Put all the committers in the same group, and make the repository\r
writable by that group:</p>\r
<div class="listingblock">\r
<div class="content">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jun-2006 19:51:36 UTC\r
+Last updated 09-Jul-2006 20:38:46 UTC\r
</div>\r
</div>\r
</body>\r
full shell on the machine, there is a restricted shell which only allows
users to do git pushes and pulls; see gitlink:git-shell[1].
-Put all the committers should in the same group, and make the repository
+Put all the committers in the same group, and make the repository
writable by that group:
------------------------------------------------
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-cvsexportcommmit</em> [-h] [-v] [-c] [-p] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID</p>\r
+<p><em>git-cvsexportcommit</em> [-h] [-v] [-c] [-p] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 14-May-2006 09:22:47 UTC\r
+Last updated 09-Jul-2006 20:38:36 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-cvsexportcommmit' [-h] [-v] [-c] [-p] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID
+'git-cvsexportcommit' [-h] [-v] [-c] [-p] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID
DESCRIPTION
</dt>\r
<dd>\r
<p>\r
- Remain silent even on nonexisting files\r
+ Remain silent even on nonexistent files\r
</p>\r
</dd>\r
</dl>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 09-Jul-2006 09:37:53 UTC\r
+Last updated 09-Jul-2006 20:38:37 UTC\r
</div>\r
</div>\r
</body>\r
commit with these flags.
-q::
- Remain silent even on nonexisting files
+ Remain silent even on nonexistent files
Output format
-------------
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-diff</em> [ --diff-options ] <ent>{0,2} [<path>…]</p>\r
+<p><em>git-diff</em> [ --diff-options ] <tree-ish>{0,2} [<path>…]</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
-<p>Show changes between two ents, an ent and the working tree, an\r
-ent and the index file, or the index file and the working tree.\r
+<p>Show changes between two trees, a tree and the working tree, a\r
+tree and the index file, or the index file and the working tree.\r
The combination of what is compared with what is determined by\r
-the number of ents given to the command.</p>\r
+the number of trees given to the command.</p>\r
<ul>\r
<li>\r
<p>\r
-When no <ent> is given, the working tree and the index\r
- file is compared, using <tt>git-diff-files</tt>.\r
+When no <tree-ish> is given, the working tree and the index\r
+ file are compared, using <tt>git-diff-files</tt>.\r
</p>\r
</li>\r
<li>\r
<p>\r
-When one <ent> is given, the working tree and the named\r
- tree is compared, using <tt>git-diff-index</tt>. The option\r
+When one <tree-ish> is given, the working tree and the named\r
+ tree are compared, using <tt>git-diff-index</tt>. The option\r
<tt>--cached</tt> can be given to compare the index file and\r
the named tree.\r
</p>\r
</li>\r
<li>\r
<p>\r
-When two <ent>s are given, these two trees are compared\r
+When two <tree-ish>s are given, these two trees are compared\r
using <tt>git-diff-tree</tt>.\r
</p>\r
</li>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Jun-2006 07:24:26 UTC\r
+Last updated 09-Jul-2006 20:38:38 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-diff' [ --diff-options ] <ent>{0,2} [<path>...]
+'git-diff' [ --diff-options ] <tree-ish>{0,2} [<path>...]
DESCRIPTION
-----------
-Show changes between two ents, an ent and the working tree, an
-ent and the index file, or the index file and the working tree.
+Show changes between two trees, a tree and the working tree, a
+tree and the index file, or the index file and the working tree.
The combination of what is compared with what is determined by
-the number of ents given to the command.
+the number of trees given to the command.
-* When no <ent> is given, the working tree and the index
- file is compared, using `git-diff-files`.
+* When no <tree-ish> is given, the working tree and the index
+ file are compared, using `git-diff-files`.
-* When one <ent> is given, the working tree and the named
- tree is compared, using `git-diff-index`. The option
+* When one <tree-ish> is given, the working tree and the named
+ tree are compared, using `git-diff-index`. The option
`--cached` can be given to compare the index file and
the named tree.
-* When two <ent>s are given, these two trees are compared
+* When two <tree-ish>s are given, these two trees are compared
using `git-diff-tree`.
OPTIONS
<repository> without <refspec> parameters on the command\r
line, <refspec> specified on <tt>Push:</tt> lines or <tt>Pull:</tt>\r
lines are used for <tt>git-push</tt> and <tt>git-fetch</tt>/<tt>git-pull</tt>,\r
-respectively. Multiple <tt>Push:</tt> and and <tt>Pull:</tt> lines may\r
+respectively. Multiple <tt>Push:</tt> and <tt>Pull:</tt> lines may\r
be specified for additional branch mappings.</p>\r
<p>The name of a file in <tt>$GIT_DIR/branches</tt> directory can be\r
specified as an older notation short-hand; the named\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Mar-2006 00:31:25 UTC\r
+Last updated 09-Jul-2006 20:38:38 UTC\r
</div>\r
</div>\r
</body>\r
<div class="sectionbody">\r
<p>This command creates an empty git repository - basically a <tt>.git</tt> directory\r
with subdirectories for <tt>objects</tt>, <tt>refs/heads</tt>, <tt>refs/tags</tt>, and\r
-templated files.\r
+template files.\r
An initial <tt>HEAD</tt> file that references the HEAD of the master branch\r
is also created.</p>\r
<p>If <tt>--template=<template_directory></tt> is specified, <tt><template_directory></tt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 29-Apr-2006 07:01:33 UTC\r
+Last updated 09-Jul-2006 20:38:39 UTC\r
</div>\r
</div>\r
</body>\r
-----------
This command creates an empty git repository - basically a `.git` directory
with subdirectories for `objects`, `refs/heads`, `refs/tags`, and
-templated files.
+template files.
An initial `HEAD` file that references the HEAD of the master branch
is also created.
<dd>\r
<p>\r
If any file doesn't begin with a From line, assume it is a\r
- single mail message instead of signalling error.\r
+ single mail message instead of signaling error.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Mar-2006 00:31:29 UTC\r
+Last updated 09-Jul-2006 20:38:39 UTC\r
</div>\r
</div>\r
</body>\r
-b::
If any file doesn't begin with a From line, assume it is a
- single mail message instead of signalling error.
+ single mail message instead of signaling error.
-d<prec>::
Instead of the default 4 digits with leading zeros,
your local modifications interfere with the merge, again, it\r
stops before touching anything.</p>\r
<p>So in the above two "failed merge" case, you do not have to\r
-worry about lossage of data --- you simply were not ready to do\r
+worry about loss of data --- you simply were not ready to do\r
a merge, so no merge happened at all. You may want to finish\r
whatever you were in the middle of doing, and retry the same\r
pull after you are done and ready.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Jun-2006 23:46:45 UTC\r
+Last updated 09-Jul-2006 20:38:39 UTC\r
</div>\r
</div>\r
</body>\r
stops before touching anything.
So in the above two "failed merge" case, you do not have to
-worry about lossage of data --- you simply were not ready to do
+worry about loss of data --- you simply were not ready to do
a merge, so no merge happened at all. You may want to finish
whatever you were in the middle of doing, and retry the same
pull after you are done and ready.
<p>A git tag of the form p4/xx is created for every change imported from\r
the Perforce repository where xx is the Perforce changeset number.\r
Therefore after the import you can use git to access any commit by its\r
-Perforce number, eg. git show p4/327.</p>\r
+Perforce number, e.g. git show p4/327.</p>\r
<p>The tag associated with the HEAD commit is also how <tt>git-p4import</tt>\r
determines if there are new changes to incrementally import from the\r
Perforce repository.</p>\r
</div>\r
<h2>Notes</h2>\r
<div class="sectionbody">\r
-<p>You can interrupt the import (eg. ctrl-c) at any time and restart it\r
+<p>You can interrupt the import (e.g. ctrl-c) at any time and restart it\r
without worry.</p>\r
<p>Author information is automatically determined by querying the\r
Perforce "users" table using the id associated with each change.\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 18-Jun-2006 00:21:51 UTC\r
+Last updated 09-Jul-2006 20:38:40 UTC\r
</div>\r
</div>\r
</body>\r
A git tag of the form p4/xx is created for every change imported from
the Perforce repository where xx is the Perforce changeset number.
Therefore after the import you can use git to access any commit by its
-Perforce number, eg. git show p4/327.
+Perforce number, e.g. git show p4/327.
The tag associated with the HEAD commit is also how `git-p4import`
determines if there are new changes to incrementally import from the
Notes
-----
-You can interrupt the import (eg. ctrl-c) at any time and restart it
+You can interrupt the import (e.g. ctrl-c) at any time and restart it
without worry.
Author information is automatically determined by querying the
</dt>\r
<dd>\r
<p>\r
- Processes all packs. Any filenames on the commandline are ignored.\r
+ Processes all packs. Any filenames on the command line are ignored.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Mar-2006 00:31:30 UTC\r
+Last updated 09-Jul-2006 20:38:40 UTC\r
</div>\r
</div>\r
</body>\r
--all::
- Processes all packs. Any filenames on the commandline are ignored.
+ Processes all packs. Any filenames on the command line are ignored.
--alt-odb::
Don't require objects present in packs from alternate object
<repository> without <refspec> parameters on the command\r
line, <refspec> specified on <tt>Push:</tt> lines or <tt>Pull:</tt>\r
lines are used for <tt>git-push</tt> and <tt>git-fetch</tt>/<tt>git-pull</tt>,\r
-respectively. Multiple <tt>Push:</tt> and and <tt>Pull:</tt> lines may\r
+respectively. Multiple <tt>Push:</tt> and <tt>Pull:</tt> lines may\r
be specified for additional branch mappings.</p>\r
<p>The name of a file in <tt>$GIT_DIR/branches</tt> directory can be\r
specified as an older notation short-hand; the named\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Jun-2006 23:46:45 UTC\r
+Last updated 09-Jul-2006 20:38:41 UTC\r
</div>\r
</div>\r
</body>\r
<dd>\r
<p>\r
Usually, the command refuses to update a remote ref that is\r
- not a descendent of the local ref used to overwrite it.\r
+ not a descendant of the local ref used to overwrite it.\r
This flag disables the check. This can cause the\r
remote repository to lose commits; use it with care.\r
</p>\r
<repository> without <refspec> parameters on the command\r
line, <refspec> specified on <tt>Push:</tt> lines or <tt>Pull:</tt>\r
lines are used for <tt>git-push</tt> and <tt>git-fetch</tt>/<tt>git-pull</tt>,\r
-respectively. Multiple <tt>Push:</tt> and and <tt>Pull:</tt> lines may\r
+respectively. Multiple <tt>Push:</tt> and <tt>Pull:</tt> lines may\r
be specified for additional branch mappings.</p>\r
<p>The name of a file in <tt>$GIT_DIR/branches</tt> directory can be\r
specified as an older notation short-hand; the named\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Mar-2006 00:31:32 UTC\r
+Last updated 09-Jul-2006 20:38:41 UTC\r
</div>\r
</div>\r
</body>\r
-f, \--force::
Usually, the command refuses to update a remote ref that is
- not a descendent of the local ref used to overwrite it.
+ not a descendant of the local ref used to overwrite it.
This flag disables the check. This can cause the
remote repository to lose commits; use it with care.
<div class="content">\r
<pre><tt>% git repo-config core.filemode true</tt></pre>\r
</div></div>\r
-<p>The hypothetic proxy command entries actually have a postfix to discern\r
-to what URL they apply. Here is how to change the entry for kernel.org\r
+<p>The hypothetical proxy command entries actually have a postfix to discern\r
+what URL they apply to. Here is how to change the entry for kernel.org\r
to "ssh".</p>\r
<div class="listingblock">\r
<div class="content">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jul-2006 02:03:32 UTC\r
+Last updated 09-Jul-2006 20:38:42 UTC\r
</div>\r
</div>\r
</body>\r
% git repo-config core.filemode true
------------
-The hypothetic proxy command entries actually have a postfix to discern
-to what URL they apply. Here is how to change the entry for kernel.org
+The hypothetical proxy command entries actually have a postfix to discern
+what URL they apply to. Here is how to change the entry for kernel.org
to "ssh".
------------
<dd>\r
<p>\r
Similar to <tt>--objects</tt>, but also print the IDs of\r
- excluded commits refixed with a <tt>-</tt> character. This is\r
+ excluded commits prefixed with a <tt>-</tt> character. This is\r
used by <tt>git-pack-objects</tt> to build <em>thin</em> pack, which\r
records objects in deltified form based on objects\r
contained in these excluded commits to reduce network\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jul-2006 06:05:13 UTC\r
+Last updated 09-Jul-2006 20:38:43 UTC\r
</div>\r
</div>\r
</body>\r
--objects-edge::
Similar to `--objects`, but also print the IDs of
- excluded commits refixed with a `-` character. This is
+ excluded commits prefixed with a `-` character. This is
used by `git-pack-objects` to build 'thin' pack, which
records objects in deltified form based on objects
contained in these excluded commits to reduce network
</p>\r
<div class="literalblock">\r
<div class="content">\r
-<pre><tt>gitk is a simple TK GUI for browsing history of GIT repositories easily.</tt></pre>\r
+<pre><tt>gitk is a simple Tk GUI for browsing history of GIT repositories easily.</tt></pre>\r
</div></div>\r
</li>\r
<li>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Jun-2006 07:24:40 UTC\r
+Last updated 09-Jul-2006 20:38:47 UTC\r
</div>\r
</div>\r
</body>\r
- *gitk* (shipped with git-core)
- gitk is a simple TK GUI for browsing history of GIT repositories easily.
+ gitk is a simple Tk GUI for browsing history of GIT repositories easily.
- *gitview* (contrib/)
to the other end over the git protocol.</p>\r
<p>This command is usually not invoked directly by the end user.\r
The UI for the protocol is on the <em>git-tar-tree</em> side, and the\r
-program pair is meant to be used to get a tar achive from a\r
+program pair is meant to be used to get a tar archive from a\r
remote repository.</p>\r
</div>\r
<h2>OPTIONS</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jun-2006 19:51:33 UTC\r
+Last updated 09-Jul-2006 20:38:43 UTC\r
</div>\r
</div>\r
</body>\r
This command is usually not invoked directly by the end user.
The UI for the protocol is on the 'git-tar-tree' side, and the
-program pair is meant to be used to get a tar achive from a
+program pair is meant to be used to get a tar archive from a
remote repository.
<div class="sectionbody">\r
<p>Starting from 0.99.9 (actually mid 0.99.8.GIT), <tt>.git/config</tt> file\r
is used to hold per-repository configuration options. It is a\r
-simple text file modelled after <tt>.ini</tt> format familiar to some\r
+simple text file modeled after <tt>.ini</tt> format familiar to some\r
people. Here is an example:</p>\r
<div class="listingblock">\r
<div class="content">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 22-Jun-2006 19:49:27 UTC\r
+Last updated 09-Jul-2006 20:38:44 UTC\r
</div>\r
</div>\r
</body>\r
Starting from 0.99.9 (actually mid 0.99.8.GIT), `.git/config` file
is used to hold per-repository configuration options. It is a
-simple text file modelled after `.ini` format familiar to some
+simple text file modeled after `.ini` format familiar to some
people. Here is an example:
------------
<p>\r
Favorite synonym to "<a href="#ref_tree-ish">tree-ish</a>" by some total geeks. See\r
<tt>http://en.wikipedia.org/wiki/Ent_(Middle-earth)</tt> for an in-depth\r
- explanation.\r
+ explanation. Avoid this term, not to confuse people.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jun-2006 19:51:37 UTC\r
+Last updated 09-Jul-2006 20:38:48 UTC\r
</div>\r
</div>\r
</body>\r
ent::
Favorite synonym to "tree-ish" by some total geeks. See
`http://en.wikipedia.org/wiki/Ent_(Middle-earth)` for an in-depth
- explanation.
+ explanation. Avoid this term, not to confuse people.
fast forward::
A fast-forward is a special type of merge where you have
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 12-Feb-2006 13:31:35 UTC\r
+Last updated 09-Jul-2006 20:38:47 UTC\r
</div>\r
</div>\r
</body>\r
and at this point "git bisect" will churn for a while, and tell you what
the mid-point between those two commits are, and check that state out as
-the head of the bew "bisect" branch.
+the head of the new "bisect" branch.
Compile and reboot.
The two commits #2' and #3' in the above picture record the same
changes your e-mail submission for #2 and #3 contained, but
-probably with the new sign-off line added by the upsteam
+probably with the new sign-off line added by the upstream
maintainer and definitely with different committer and ancestry
information, they are different objects from #2 and #3 commits.
<repository> without <refspec> parameters on the command
line, <refspec> specified on `Push:` lines or `Pull:`
lines are used for `git-push` and `git-fetch`/`git-pull`,
-respectively. Multiple `Push:` and and `Pull:` lines may
+respectively. Multiple `Push:` and `Pull:` lines may
be specified for additional branch mappings.
The name of a file in `$GIT_DIR/branches` directory can be