used in combination with repositories found automatically in
a .git directory (i.e. $GIT_DIR is not set).
This can be overridden by the GIT_WORK_TREE environment
- variable and the '--work-tree' command line option.
+ variable and the '--work-tree' command line option. It can be
+ a absolute path or relative path to the directory specified by
+ --git-dir or GIT_DIR.
+ Note: If --git-dir or GIT_DIR are specified but none of
+ --work-tree, GIT_WORK_TREE and core.worktree is specified,
+ the current working directory is regarded as the top directory
+ of your working tree.
core.logAllRefUpdates::
Enable the reflog. Updates to a ref <ref> is logged to the file
used in combination with repositories found automatically in\r
a .git directory (i.e. $GIT_DIR is not set).\r
This can be overridden by the GIT_WORK_TREE environment\r
- variable and the <em>--work-tree</em> command line option.\r
+ variable and the <em>--work-tree</em> command line option. It can be\r
+ a absolute path or relative path to the directory specified by\r
+ --git-dir or GIT_DIR.\r
+ Note: If --git-dir or GIT_DIR are specified but none of\r
+ --work-tree, GIT_WORK_TREE and core.worktree is specified,\r
+ the current working directory is regarded as the top directory\r
+ of your working tree.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 26-Apr-2008 02:23:16 UTC\r
+Last updated 30-Apr-2008 08:42:07 UTC\r
</div>\r
</div>\r
</body>\r
An object to treat as the head of an unreachability trace.\r
</p>\r
<p>If no objects are given, git-fsck defaults to using the\r
-index file and all SHA1 references in .git/refs/* as heads.</p>\r
+index file, all SHA1 references in .git/refs/*, and all reflogs (unless\r
+--no-reflogs is given) as heads.</p>\r
</dd>\r
<dt>\r
--unreachable\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:22 UTC\r
+Last updated 30-Apr-2008 08:42:07 UTC\r
</div>\r
</div>\r
</body>\r
An object to treat as the head of an unreachability trace.
+
If no objects are given, git-fsck defaults to using the
-index file and all SHA1 references in .git/refs/* as heads.
+index file, all SHA1 references in .git/refs/*, and all reflogs (unless
+--no-reflogs is given) as heads.
--unreachable::
Print out objects that exist but that aren't readable from any
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
+<div class="admonitionblock">\r
+<table><tr>\r
+<td class="icon">\r
+<div class="title">Note</div>\r
+</td>\r
+<td class="content">In most cases, users should run <a href="git-gc.html">git-gc(1)</a>, which calls\r
+git-prune. See the section "NOTES", below.</td>\r
+</tr></table>\r
+</div>\r
<p>This runs <tt>git-fsck --unreachable</tt> using all the refs\r
available in <tt>$GIT_DIR/refs</tt>, optionally with additional set of\r
objects specified on the command line, and prunes all\r
<pre><tt>$ git prune $(cd ../another && $(git-rev-parse --all))</tt></pre>\r
</div></div>\r
</div>\r
+<h2>Notes</h2>\r
+<div class="sectionbody">\r
+<p>In most cases, users will not need to call git-prune directly, but\r
+should instead call <a href="git-gc.html">git-gc(1)</a>, which handles pruning along with\r
+many other housekeeping tasks.</p>\r
+<p>For a description of which objects are considered for pruning, see\r
+git-fsck's --unreachable option.</p>\r
+</div>\r
+<h2>See Also</h2>\r
+<div class="sectionbody">\r
+<p><a href="git-fsck.html">git-fsck(1)</a>,\r
+<a href="git-gc.html">git-gc(1)</a>,\r
+<a href="git-reflog.html">git-reflog(1)</a></p>\r
+</div>\r
<h2>Author</h2>\r
<div class="sectionbody">\r
<p>Written by Linus Torvalds <torvalds@osdl.org></p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:36 UTC\r
+Last updated 30-Apr-2008 08:42:08 UTC\r
</div>\r
</div>\r
</body>\r
DESCRIPTION
-----------
+NOTE: In most cases, users should run linkgit:git-gc[1], which calls
+git-prune. See the section "NOTES", below.
+
This runs `git-fsck --unreachable` using all the refs
available in `$GIT_DIR/refs`, optionally with additional set of
objects specified on the command line, and prunes all
$ git prune $(cd ../another && $(git-rev-parse --all))
------------
+Notes
+-----
+
+In most cases, users will not need to call git-prune directly, but
+should instead call linkgit:git-gc[1], which handles pruning along with
+many other housekeeping tasks.
+
+For a description of which objects are considered for pruning, see
+git-fsck's --unreachable option.
+
+See Also
+--------
+
+linkgit:git-fsck[1],
+linkgit:git-gc[1],
+linkgit:git-reflog[1]
+
Author
------
Written by Linus Torvalds <torvalds@osdl.org>
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-unpack-objects</em> [-n] [-q] [-r] <pack-file</p>\r
+<p><em>git-unpack-objects</em> [-n] [-q] [-r] [--strict] <pack-file</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 09-Apr-2008 09:38:28 UTC\r
+Last updated 30-Apr-2008 08:42:08 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-unpack-objects' [-n] [-q] [-r] <pack-file
+'git-unpack-objects' [-n] [-q] [-r] [--strict] <pack-file
DESCRIPTION
<dd>\r
<p>\r
Set the path to the repository. This can also be controlled by\r
- setting the GIT_DIR environment variable.\r
+ setting the GIT_DIR environment variable. It can be an absolute\r
+ path or relative path to current working directory.\r
</p>\r
</dd>\r
<dt>\r
a .git directory (i.e. $GIT_DIR is not set).\r
This can also be controlled by setting the GIT_WORK_TREE\r
environment variable and the core.worktree configuration\r
- variable.\r
+ variable. It can be an absolute path or relative path to\r
+ the directory specified by --git-dir or GIT_DIR.\r
+ Note: If --git-dir or GIT_DIR are specified but none of\r
+ --work-tree, GIT_WORK_TREE and core.worktree is specified,\r
+ the current working directory is regarded as the top directory\r
+ of your working tree.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 21-Apr-2008 00:47:32 UTC\r
+Last updated 30-Apr-2008 08:42:10 UTC\r
</div>\r
</div>\r
</body>\r
--git-dir=<path>::
Set the path to the repository. This can also be controlled by
- setting the GIT_DIR environment variable.
+ setting the GIT_DIR environment variable. It can be an absolute
+ path or relative path to current working directory.
--work-tree=<path>::
Set the path to the working tree. The value will not be
a .git directory (i.e. $GIT_DIR is not set).
This can also be controlled by setting the GIT_WORK_TREE
environment variable and the core.worktree configuration
- variable.
+ variable. It can be an absolute path or relative path to
+ the directory specified by --git-dir or GIT_DIR.
+ Note: If --git-dir or GIT_DIR are specified but none of
+ --work-tree, GIT_WORK_TREE and core.worktree is specified,
+ the current working directory is regarded as the top directory
+ of your working tree.
--bare::
Treat the repository as a bare repository. If GIT_DIR
</p>\r
</dd>\r
<dt>\r
+--merge\r
+</dt>\r
+<dd>\r
+<p>\r
+ After an attempt to merge stops with conflicts, show the commits on\r
+ the history between two branches (i.e. the HEAD and the MERGE_HEAD)\r
+ that modify the conflicted files.\r
+</p>\r
+</dd>\r
+<dt>\r
<revs>\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 13-Apr-2008 05:32:58 UTC\r
+Last updated 30-Apr-2008 08:42:09 UTC\r
</div>\r
</div>\r
</body>\r
Show all branches.
+--merge::
+
+ After an attempt to merge stops with conflicts, show the commits on
+ the history between two branches (i.e. the HEAD and the MERGE_HEAD)
+ that modify the conflicted files.
+
<revs>::
Limit the revisions to show. This can be either a single revision