Autogenerated HTML docs for v1.8.1.2-545-g2f19ad

1 files changed, 41 insertions, 32 deletions

diff --git a/gitglossary.html b/gitglossary.html
index 199ade0d3..0126b311e 100644
--- a/gitglossary.html
+++ b/gitglossary.html
@@ -737,7 +737,7 @@ gitglossary(7) Manual Page
 <h2>NAME</h2>

 <div class="sectionbody">

 <p>gitglossary -

-   A GIT Glossary

+   A Git Glossary

 </p>

 </div>

 </div>

@@ -770,7 +770,7 @@ gitglossary(7) Manual Page
         A bare repository is normally an appropriately

         named <a href="#def_directory">directory</a> with a <code>.git</code> suffix that does not

         have a locally checked-out copy of any of the files under

-        revision control. That is, all of the <code>git</code>

+        revision control. That is, all of the Git

         administrative and control files that would normally be present in the

         hidden <code>.git</code> sub-directory are directly present in the

         <code>repository.git</code> directory instead,

@@ -795,7 +795,7 @@ gitglossary(7) Manual Page
         <a href="#def_commit">commit</a> on a branch is referred to as the tip of

         that branch.  The tip of the branch is referenced by a branch

         <a href="#def_head">head</a>, which moves forward as additional development

-        is done on the branch.  A single git

+        is done on the branch.  A single Git

         <a href="#def_repository">repository</a> can track an arbitrary number of

         branches, but your <a href="#def_working_tree">working tree</a> is

         associated with just one of them (the "current" or "checked out"

@@ -825,9 +825,9 @@ gitglossary(7) Manual Page
 </dt>

 <dd>

 <p>

-        BitKeeper/cvsps speak for "<a href="#def_commit">commit</a>". Since git does not

+        BitKeeper/cvsps speak for "<a href="#def_commit">commit</a>". Since Git does not

         store changes, but states, it really does not make sense to use the term

-        "changesets" with git.

+        "changesets" with Git.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -850,7 +850,7 @@ gitglossary(7) Manual Page
 <p>

         In <a href="#def_SCM">SCM</a> jargon, "cherry pick" means to choose a subset of

         changes out of a series of changes (typically commits) and record them

-        as a new series of changes on top of a different codebase. In GIT, this is

+        as a new series of changes on top of a different codebase. In Git, this is

         performed by the "git cherry-pick" command to extract the change introduced

         by an existing <a href="#def_commit">commit</a> and to record it based on the tip

         of the current <a href="#def_branch">branch</a> as a new commit.

@@ -872,14 +872,14 @@ gitglossary(7) Manual Page
 <dd>

 <p>

         As a noun: A single point in the

-        git history; the entire history of a project is represented as a

+        Git history; the entire history of a project is represented as a

         set of interrelated commits.  The word "commit" is often

-        used by git in the same places other revision control systems

+        used by Git in the same places other revision control systems

         use the words "revision" or "version".  Also used as a short

         hand for <a href="#def_commit_object">commit object</a>.

 </p>

 <div class="paragraph"><p>As a verb: The action of storing a new snapshot of the project&#8217;s

-state in the git history, by creating a new commit representing the current

+state in the Git history, by creating a new commit representing the current

 state of the <a href="#def_index">index</a> and advancing <a href="#def_HEAD">HEAD</a>

 to point at the new commit.</p></div>

 </dd>

@@ -896,11 +896,11 @@ to point at the new commit.</p></div>
 </p>

 </dd>

 <dt class="hdlist1">

-<a id="def_core_git"></a>core git

+<a id="def_core_git"></a>core Git

 </dt>

 <dd>

 <p>

-        Fundamental data structures and utilities of git. Exposes only limited

+        Fundamental data structures and utilities of Git. Exposes only limited

         source code management tools.

 </p>

 </dd>

@@ -932,7 +932,7 @@ to point at the new commit.</p></div>
 <dd>

 <p>

         Normally the <a href="#def_HEAD">HEAD</a> stores the name of a

-        <a href="#def_branch">branch</a>.  However, git also allows you to <a href="#def_checkout">check out</a>

+        <a href="#def_branch">branch</a>.  However, Git also allows you to <a href="#def_checkout">check out</a>

         an arbitrary <a href="#def_commit">commit</a> that isn&#8217;t necessarily the tip of any

         particular branch.  In this case HEAD is said to be "detached".

 </p>

@@ -1014,13 +1014,13 @@ to point at the new commit.</p></div>
 </dt>

 <dd>

 <p>

-        Linus Torvalds originally designed git to be a user space file system,

+        Linus Torvalds originally designed Git to be a user space file system,

         i.e. the infrastructure to hold files and directories. That ensured the

-        efficiency and speed of git.

+        efficiency and speed of Git.

 </p>

 </dd>

 <dt class="hdlist1">

-<a id="def_git_archive"></a>git archive

+<a id="def_git_archive"></a>Git archive

 </dt>

 <dd>

 <p>

@@ -1028,13 +1028,22 @@ to point at the new commit.</p></div>
 </p>

 </dd>

 <dt class="hdlist1">

+<a id="def_gitfile"></a>gitfile

+</dt>

+<dd>

+<p>

+        A plain file <code>.git</code> at the root of a working tree that

+        points at the directory that is the real repository.

+</p>

+</dd>

+<dt class="hdlist1">

 <a id="def_grafts"></a>grafts

 </dt>

 <dd>

 <p>

         Grafts enables two otherwise different lines of development to be joined

         together by recording fake ancestry information for commits. This way

-        you can make git pretend the set of <a href="#def_parent">parents</a> a <a href="#def_commit">commit</a> has

+        you can make Git pretend the set of <a href="#def_parent">parents</a> a <a href="#def_commit">commit</a> has

         is different from what was recorded when the commit was

         created. Configured via the <code>.git/info/grafts</code> file.

 </p>

@@ -1044,7 +1053,7 @@ to point at the new commit.</p></div>
 </dt>

 <dd>

 <p>

-        In git&#8217;s context, synonym to <a href="#def_object_name">object name</a>.

+        In Git&#8217;s context, synonym to <a href="#def_object_name">object name</a>.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1083,14 +1092,14 @@ to point at the new commit.</p></div>
 </dt>

 <dd>

 <p>

-        During the normal execution of several git commands, call-outs are made

+        During the normal execution of several Git commands, call-outs are made

         to optional scripts that allow a developer to add functionality or

         checking. Typically, the hooks allow for a command to be pre-verified

         and potentially aborted, and allow for a post-notification after the

         operation is done. The hook scripts are found in the

         <code>$GIT_DIR/hooks/</code> directory, and are enabled by simply

         removing the <code>.sample</code> suffix from the filename. In earlier versions

-        of git you had to make them executable.

+        of Git you had to make them executable.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1122,7 +1131,7 @@ to point at the new commit.</p></div>
 <dd>

 <p>

         The default development <a href="#def_branch">branch</a>. Whenever you

-        create a git <a href="#def_repository">repository</a>, a branch named

+        create a Git <a href="#def_repository">repository</a>, a branch named

         "master" is created, and becomes the active branch. In most

         cases, this contains the local development, though that is

         purely by convention and is not required.

@@ -1158,7 +1167,7 @@ This commit is referred to as a "merge commit", or sometimes just a
 </dt>

 <dd>

 <p>

-        The unit of storage in git. It is uniquely identified by the

+        The unit of storage in Git. It is uniquely identified by the

         <a href="#def_SHA1">SHA1</a> of its contents. Consequently, an

         object can not be changed.

 </p>

@@ -1313,7 +1322,7 @@ top <code>/</code>
 </div></div>

 <div class="paragraph"><p>Currently only the slash <code>/</code> is recognized as the "magic signature",

 but it is envisioned that we will support more types of magic in later

-versions of git.</p></div>

+versions of Git.</p></div>

 <div class="paragraph"><p>A pathspec with only a colon means "there is no pathspec". This form

 should not be combined with other pathspec.</p></div>

 </dd>

@@ -1344,7 +1353,7 @@ should not be combined with other pathspec.</p></div>
 </dt>

 <dd>

 <p>

-        Cute name for <a href="#def_core_git">core git</a>.

+        Cute name for <a href="#def_core_git">core Git</a>.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1353,8 +1362,8 @@ should not be combined with other pathspec.</p></div>
 <dd>

 <p>

         Cute name for programs and program suites depending on

-        <a href="#def_core_git">core git</a>, presenting a high level access to

-        core git. Porcelains expose more of a <a href="#def_SCM">SCM</a>

+        <a href="#def_core_git">core Git</a>, presenting a high level access to

+        core Git. Porcelains expose more of a <a href="#def_SCM">SCM</a>

         interface than the <a href="#def_plumbing">plumbing</a>.

 </p>

 </dd>

@@ -1454,7 +1463,7 @@ should not be combined with other pathspec.</p></div>
 </dt>

 <dd>

 <p>

-        A regular git <a href="#def_branch">branch</a> that is used to follow changes from

+        A regular Git <a href="#def_branch">branch</a> that is used to follow changes from

         another <a href="#def_repository">repository</a>. A remote-tracking

         branch should not contain direct modifications or have local commits

         made to it. A remote-tracking branch can usually be

@@ -1526,7 +1535,7 @@ should not be combined with other pathspec.</p></div>
 <p>

         A shallow <a href="#def_repository">repository</a> has an incomplete

         history some of whose <a href="#def_commit">commits</a> have <a href="#def_parent">parents</a> cauterized away (in other

-        words, git is told to pretend that these commits do not have the

+        words, Git is told to pretend that these commits do not have the

         parents, even though they are recorded in the <a href="#def_commit_object">commit         object</a>). This is sometimes useful when you are interested only in the

         recent history of a project even though the real history recorded in the

         upstream is much larger. A shallow repository

@@ -1556,9 +1565,9 @@ should not be combined with other pathspec.</p></div>
         object of an arbitrary type (typically a tag points to either a

         <a href="#def_tag_object">tag</a> or a <a href="#def_commit_object">commit object</a>).

         In contrast to a <a href="#def_head">head</a>, a tag is not updated by

-        the <code>commit</code> command. A git tag has nothing to do with a Lisp

+        the <code>commit</code> command. A Git tag has nothing to do with a Lisp

         tag (which would be called an <a href="#def_object_type">object type</a>

-        in git&#8217;s context). A tag is most typically used to mark a particular

+        in Git&#8217;s context). A tag is most typically used to mark a particular

         point in the commit ancestry <a href="#def_chain">chain</a>.

 </p>

 </dd>

@@ -1578,7 +1587,7 @@ should not be combined with other pathspec.</p></div>
 </dt>

 <dd>

 <p>

-        A regular git <a href="#def_branch">branch</a> that is used by a developer to

+        A regular Git <a href="#def_branch">branch</a> that is used by a developer to

         identify a conceptual line of development. Since branches are very easy

         and inexpensive, it is often desirable to have several small branches

         that each contain very well defined concepts or small incremental yet

@@ -1660,7 +1669,7 @@ should not be combined with other pathspec.</p></div>
 <div class="paragraph"><p><a href="gittutorial.html">gittutorial(7)</a>,

 <a href="gittutorial-2.html">gittutorial-2(7)</a>,

 <a href="gitcvs-migration.html">gitcvs-migration(7)</a>,

-<a href="everyday.html">Everyday git</a>,

+<a href="everyday.html">Everyday Git</a>,

 <a href="user-manual.html">The Git User&#8217;s Manual</a></p></div>

 </div>

 </div>

@@ -1674,7 +1683,7 @@ should not be combined with other pathspec.</p></div>
 <div id="footnotes"><hr /></div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2011-11-15 13:45:02 PST

+Last updated 2013-02-05 21:07:26 PST

 </div>

 </div>

 </body>