</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-branch</em> [(-d | -D) <branchname>] | [[-f] <branchname> [<start-point>]]</p>\r
+<div class="verseblock">\r
+<div class="content"><em>git-branch</em> [[-f] <branchname> [<start-point>]]\r
+<em>git-branch</em> (-d | -D) <branchname></div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
<p>If no argument is provided, show available branches and mark current\r
-branch with star. Otherwise, create a new branch of name <branchname>.</p>\r
-<p>If a starting point is also specified, that will be where the branch is\r
+branch with star. Otherwise, create a new branch of name <branchname>.\r
+If a starting point is also specified, that will be where the branch is\r
created, otherwise it will be created at the current HEAD.</p>\r
+<p>With a <tt>-d</tt> or <tt>-D</tt> option, <tt><branchname></tt> will be deleted.</p>\r
</div>\r
<h2>OPTIONS</h2>\r
<div class="sectionbody">\r
<h3>Examples</h3>\r
<dl>\r
<dt>\r
-Start development off of a know tag\r
+Start development off of a known tag\r
</dt>\r
<dd>\r
<div class="listingblock">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Mar-2006 00:31:21 UTC\r
+Last updated 18-Mar-2006 07:45:34 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-branch' [(-d | -D) <branchname>] | [[-f] <branchname> [<start-point>]]
+[verse]
+'git-branch' [[-f] <branchname> [<start-point>]]
+'git-branch' (-d | -D) <branchname>
DESCRIPTION
-----------
If no argument is provided, show available branches and mark current
branch with star. Otherwise, create a new branch of name <branchname>.
-
If a starting point is also specified, that will be where the branch is
created, otherwise it will be created at the current HEAD.
+With a `-d` or `-D` option, `<branchname>` will be deleted.
+
+
OPTIONS
-------
-d::
Examples
~~~~~~~~
-Start development off of a know tag::
+Start development off of a known tag::
+
------------
$ git clone git://git.kernel.org/pub/scm/.../linux-2.6 my2.6
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-checkout</em> [-f] [-b <new_branch>] [-m] [<branch>] [<paths>…]</p>\r
+<div class="verseblock">\r
+<div class="content"><em>git-checkout</em> [-f] [-b <new_branch>] [-m] [<branch>]\r
+<em>git-checkout</em> [-m] [<branch>] <paths>…</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
-<p>When <paths> are not given, this command switches branches, by\r
+<p>When <paths> are not given, this command switches branches by\r
updating the index and working tree to reflect the specified\r
branch, <branch>, and updating HEAD to be <branch> or, if\r
-specified, <new_branch>.</p>\r
+specified, <new_branch>. Using -b will cause <new_branch> to\r
+be created.</p>\r
<p>When <paths> are given, this command does <strong>not</strong> switch\r
branches. It updates the named paths in the working tree from\r
the index file (i.e. it runs <tt>git-checkout-index -f -u</tt>). In\r
</dt>\r
<dd>\r
<p>\r
- Force an re-read of everything.\r
+ Force a re-read of everything.\r
</p>\r
</dd>\r
<dt>\r
</dt>\r
<dd>\r
<p>\r
- If you have local modifications to a file that is\r
- different between the current branch and the branch you\r
- are switching to, the command refuses to switch\r
- branches, to preserve your modifications in context.\r
- With this option, a three-way merge between the current\r
+ If you have local modifications to one or more files that\r
+ are different between the current branch and the branch to\r
+ which you are switching, the command refuses to switch\r
+ branches in order to preserve your modifications in context.\r
+ However, with this option, a three-way merge between the current\r
branch, your working tree contents, and the new branch\r
is done, and you will be on the new branch.\r
</p>\r
<li>\r
<p>\r
After working in a wrong branch, switching to the correct\r
-branch you would want to is done with:\r
+branch would be done using:\r
</p>\r
<div class="listingblock">\r
<div class="content">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Mar-2006 00:31:21 UTC\r
+Last updated 18-Mar-2006 07:45:34 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-checkout' [-f] [-b <new_branch>] [-m] [<branch>] [<paths>...]
+[verse]
+'git-checkout' [-f] [-b <new_branch>] [-m] [<branch>]
+'git-checkout' [-m] [<branch>] <paths>...
DESCRIPTION
-----------
-When <paths> are not given, this command switches branches, by
+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>.
+specified, <new_branch>. Using -b will cause <new_branch> to
+be created.
When <paths> are given, this command does *not* switch
branches. It updates the named paths in the working tree from
OPTIONS
-------
-f::
- Force an re-read of everything.
+ Force a re-read of everything.
-b::
Create a new branch and start it at <branch>.
-m::
- If you have local modifications to a file that is
- different between the current branch and the branch you
- are switching to, the command refuses to switch
- branches, to preserve your modifications in context.
- With this option, a three-way merge between the current
+ If you have local modifications to one or more files that
+ are different between the current branch and the branch to
+ which you are switching, the command refuses to switch
+ branches in order to preserve your modifications in context.
+ However, with this option, a three-way merge between the current
branch, your working tree contents, and the new branch
is done, and you will be on the new branch.
+
------------
. After working in a wrong branch, switching to the correct
-branch you would want to is done with:
+branch would be done using:
+
------------
$ git checkout mytopic
<em>-a</em> is specified, and makes a commit object. The command\r
VISUAL and EDITOR environment variables to edit the commit log\r
message.</p>\r
+<p>Several environment variable are used during commits. They are\r
+documented in <a href="git-commit-tree.html">git-commit-tree(1)</a>.</p>\r
<p>This command can run <tt>commit-msg</tt>, <tt>pre-commit</tt>, and\r
<tt>post-commit</tt> hooks. See <a href="hooks.html">hooks</a> for more\r
information.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 14-Feb-2006 07:59:59 UTC\r
+Last updated 18-Mar-2006 07:45:35 UTC\r
</div>\r
</div>\r
</body>\r
VISUAL and EDITOR environment variables to edit the commit log
message.
+Several environment variable are used during commits. They are
+documented in gitlink:git-commit-tree[1].
+
+
This command can run `commit-msg`, `pre-commit`, and
`post-commit` hooks. See link:hooks.html[hooks] for more
information.
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">\r
<head>\r
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />\r
-<meta name="generator" content="AsciiDoc 7.0.1" />\r
+<meta name="generator" content="AsciiDoc 7.0.2" />\r
<style type="text/css">\r
/* Debug borders */\r
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {\r
</dt>\r
<dd>\r
<p>\r
- Provide the directory in from which templates will be used.\r
+ Provide the directory from which templates will be used.\r
+ The default template directory is <tt>/usr/share/git-core/templates</tt>.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
-<p>This simply creates an empty git repository - basically a <tt>.git</tt> directory\r
-and <tt>.git/object/??/</tt>, <tt>.git/refs/heads</tt> and <tt>.git/refs/tags</tt> directories,\r
-and links <tt>.git/HEAD</tt> symbolically to <tt>.git/refs/heads/master</tt>.</p>\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
+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
+is used as the source of the template files rather than the default.\r
+The template files include some directory structure, some suggested\r
+"exclude patterns", and copies of non-executing "hook" files. The\r
+suggested patterns and hook files are all modifiable and extensible.</p>\r
<p>If the <tt>$GIT_DIR</tt> environment variable is set then it specifies a path\r
to use instead of <tt>./.git</tt> for the base of the repository.</p>\r
<p>If the object storage directory is specified via the <tt>$GIT_OBJECT_DIRECTORY</tt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 06-Jan-2006 17:12:38 PDT\r
+Last updated 18-Mar-2006 07:45:35 UTC\r
</div>\r
</div>\r
</body>\r
OPTIONS
-------
--template=<template_directory>::
- Provide the directory in from which templates will be used.
+ Provide the directory from which templates will be used.
+ The default template directory is `/usr/share/git-core/templates`.
--shared::
Specify that the git repository is to be shared amongst several users.
DESCRIPTION
-----------
-This simply creates an empty git repository - basically a `.git` directory
-and `.git/object/??/`, `.git/refs/heads` and `.git/refs/tags` directories,
-and links `.git/HEAD` symbolically to `.git/refs/heads/master`.
+This command creates an empty git repository - basically a `.git` directory
+with subdirectories for `objects`, `refs/heads`, `refs/tags`, and
+templated files.
+An initial `HEAD` file that references the HEAD of the master branch
+is also created.
+
+If `--template=<template_directory>` is specified, `<template_directory>`
+is used as the source of the template files rather than the default.
+The template files include some directory structure, some suggested
+"exclude patterns", and copies of non-executing "hook" files. The
+suggested patterns and hook files are all modifiable and extensible.
If the `$GIT_DIR` environment variable is set then it specifies a path
to use instead of `./.git` for the base of the repository.
is set to 'true' so that directories under `$GIT_DIR` are made group writable
(and g+sx, since the git group may be not the primary group of all users).
-
Running `git-init-db` in an existing repository is safe. It will not overwrite
things that are already there. The primary reason for rerunning `git-init-db`
is to pick up newly added templates.
/\r
D---E---F---G master</tt></pre>\r
</div></div>\r
-<p>From this point, the result of the following commands:</p>\r
+<p>From this point, the result of either of the following commands:</p>\r
<div class="literalblock">\r
<div class="content">\r
<pre><tt>git-rebase master\r
/\r
D---E---F---G master</tt></pre>\r
</div></div>\r
-<p>While, starting from the same point, the result of the following\r
+<p>While, starting from the same point, the result of either of the following\r
commands:</p>\r
<div class="literalblock">\r
<div class="content">\r
</p>\r
</dd>\r
<dt>\r
-<head>\r
+<branch>\r
</dt>\r
<dd>\r
<p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Mar-2006 00:31:32 UTC\r
+Last updated 18-Mar-2006 07:45:36 UTC\r
</div>\r
</div>\r
</body>\r
/
D---E---F---G master
-From this point, the result of the following commands:
+From this point, the result of either of the following commands:
git-rebase master
git-rebase master topic
/
D---E---F---G master
-While, starting from the same point, the result of the following
+While, starting from the same point, the result of either of the following
commands:
git-rebase --onto master~1 master
<upstream>::
Upstream branch to compare against.
-<head>::
+<branch>::
Working branch; defaults to HEAD.
Author
default = heads/*\r
</tt></pre>\r
</div></div>\r
-<p>With this,<tt>git show-branch</tt> without extra parameters would show\r
+<p>With this, <tt>git show-branch</tt> without extra parameters would show\r
only the primary branches. In addition, if you happen to be on\r
your topic branch, it is shown as well.</p>\r
</div>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Mar-2006 00:31:36 UTC\r
+Last updated 18-Mar-2006 07:45:36 UTC\r
</div>\r
</div>\r
</body>\r
------------
-With this,`git show-branch` without extra parameters would show
+With this, `git show-branch` without extra parameters would show
only the primary branches. In addition, if you happen to be on
your topic branch, it is shown as well.
</p>\r
</dd>\r
<dt>\r
+<a href="git-show.html">git-show(1)</a>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Show one commit log and its diff.\r
+</p>\r
+</dd>\r
+<dt>\r
<a href="git-show-branch.html">git-show-branch(1)</a>\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Mar-2006 00:31:39 UTC\r
+Last updated 18-Mar-2006 07:45:36 UTC\r
</div>\r
</div>\r
</body>\r
gitlink:git-shortlog[1]::
Summarizes 'git log' output.
+gitlink:git-show[1]::
+ Show one commit log and its diff.
+
gitlink:git-show-branch[1]::
Show branches and their commits.