.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-CAT\-FILE" "1" "01/19/2007" "" ""
+.TH "GIT\-CAT\-FILE" "1" "02/01/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "OPTIONS"
.TP
<object>
-The sha1 identifier of the object.
+The name of the object to show. For a more complete list of ways to spell object names, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
.TP
\-t
Instead of the content, show the object type identified by <object>.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-CHECKOUT" "1" "01/17/2007" "" ""
+.TH "GIT\-CHECKOUT" "1" "02/01/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.sp
.nf
\fIgit\-checkout\fR [\-f] [\-b <new_branch> [\-l]] [\-m] [<branch>]
-\fIgit\-checkout\fR [<
branch>] <paths>\&...
+\fIgit\-checkout\fR [<
tree\-ish>] <paths>\&...
.fi
.SH "DESCRIPTION"
When <paths> are not given, this command switches branches by updating the index and working tree to reflect the specified branch, <branch>, and updating HEAD to be <branch> or, if specified, <new_branch>. Using \-b will cause <new_branch> to be created.
-When <paths> are given, this command does \fBnot\fR switch branches. It updates the named paths in the working tree from the index file (i.e. it runs git\-checkout\-index \-f \-u). In this case, \-f and \-b options are meaningless and giving either of them results in an error. <branch> argument can be used to specify a specific tree\-ish to update the index for the given paths before updating the working tree.
+When <paths> are given, this command does \fBnot\fR switch branches. It updates the named paths in the working tree from the index file (i.e. it runs git\-checkout\-index \-f \-u), or a named commit. In this case, \-f and \-b options are meaningless and giving either of them results in an error. <tree\-ish> argument can be used to specify a specific tree\-ish (i.e. commit, tag or tree) to update the index for the given paths before updating the working tree.
.SH "OPTIONS"
.TP
\-f
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT" "7" "01/29/2007" "" ""
+.TH "GIT" "7" "02/01/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "DESCRIPTION"
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high\-level operations and full access to internals.
-See this [1]\&\fItutorial\fR to get started, then see [2]\&\fIEveryday Git\fR for a useful minimum set of commands, and "man git\-commandname" for documentation of each command. CVS users may also want to read [3]\&\fICVS migration\fR.
+See this [1]\&\fItutorial\fR to get started, then see [2]\&\fIEveryday Git\fR for a useful minimum set of commands, and "man git\-commandname" for documentation of each command. CVS users may also want to read [3]\&\fICVS migration\fR. [4]\&\fIGit User's Manual\fR is still work in progress, but when finished hopefully it will guide a new user in a coherent way to git enlightenment ;\-).
The COMMAND is either a name of a Git command (see below) or an alias as defined in the configuration file (see \fBgit\-config\fR(1)).
.SH "OPTIONS"
.SH "FURTHER DOCUMENTATION"
See the references above to get started using git. The following is probably more detail than necessary for a first\-time user.
-The Discussion section below and the [4]\&\fICore tutorial\fR both provide introductions to the underlying git architecture.
+The Discussion section below and the [5]\&\fICore tutorial\fR both provide introductions to the underlying git architecture.
-See also the [5]\&\fIhowto\fR documents for some useful examples.
+See also the [6]\&\fIhowto\fR documents for some useful examples.
.SH "GIT COMMANDS"
We divide git into high level ("porcelain") commands and low level ("plumbing") commands.
.SH "HIGH\-LEVEL COMMANDS (PORCELAIN)"
For a more complete list of ways to spell object names, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
.SH "FILE/DIRECTORY STRUCTURE"
-Please see [6]\&\fIrepository layout\fR document.
+Please see [7]\&\fIrepository layout\fR document.
-Read [7]\&\fIhooks\fR for more details about each hook.
+Read [8]\&\fIhooks\fR for more details about each hook.
Higher level SCMs may provide and manage additional information in the $GIT_DIR.
.SH "TERMINOLOGY"
-Please see [8]\&\fIglossary\fR document.
+Please see [9]\&\fIglossary\fR document.
.SH "ENVIRONMENT VARIABLES"
Various git commands use the following environment variables:
.SS "The git Repository"
3.\ CVS migration
\%cvs\-migration.html
.TP 3
-4.\ Core tutorial
+4.\ Git User's Manual
+\%user\-manual.html
+.TP 3
+5.\ Core tutorial
\%core\-tutorial.html
.TP 3
-5.\ howto
+6.\ howto
\%howto\-index.html
.TP 3
-6.\ repository layout
+7.\ repository layout
\%repository\-layout.html
.TP 3
-7.\ hooks
+8.\ hooks
\%hooks.html
.TP 3
-8.\ glossary
+9.\ glossary
\%glossary.html
projects / git.git / commitdiff