</p>\r
</dd>\r
<dt>\r
+--abbrev-commit\r
+</dt>\r
+<dd>\r
+<p>\r
+ Instead of showing the full 40-byte hexadecimal commit object\r
+ name, show only handful hexdigits prefix. Non default number of\r
+ digits can be specified with "--abbrev=<n>" (which also modifies\r
+ diff output, if it is displayed).\r
+</p>\r
+<p>This should make "--pretty=oneline" a whole lot more readable for\r
+people using 80-column terminals.</p>\r
+</dd>\r
+<dt>\r
--encoding[=<encoding>]\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:01 UTC\r
+Last updated 21-Jun-2007 00:34:59 UTC\r
</div>\r
</div>\r
</body>\r
</p>\r
</dd>\r
<dt>\r
+--abbrev-commit\r
+</dt>\r
+<dd>\r
+<p>\r
+ Instead of showing the full 40-byte hexadecimal commit object\r
+ name, show only handful hexdigits prefix. Non default number of\r
+ digits can be specified with "--abbrev=<n>" (which also modifies\r
+ diff output, if it is displayed).\r
+</p>\r
+<p>This should make "--pretty=oneline" a whole lot more readable for\r
+people using 80-column terminals.</p>\r
+</dd>\r
+<dt>\r
--encoding[=<encoding>]\r
</dt>\r
<dd>\r
</dt>\r
<dd>\r
<p>\r
- Print out the ref names of any commits that are shown.\r
+ Print out the ref names of any commits that are shown.\r
+</p>\r
+</dd>\r
+<dt>\r
+--full-diff\r
+</dt>\r
+<dd>\r
+<p>\r
+ Without this flag, "git log -p <paths>…" shows commits that\r
+ touch the specified paths, and diffs about the same specified\r
+ paths. With this, the full diff is shown for commits that touch\r
+ the specified paths; this means that "<paths>…" limits only\r
+ commits, and doesn't limit diff for those commits.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:10 UTC\r
+Last updated 21-Jun-2007 00:34:59 UTC\r
</div>\r
</div>\r
</body>\r
See also gitlink:git-reflog[1].
--decorate::
- Print out the ref names of any commits that are shown.
+ Print out the ref names of any commits that are shown.
+
+--full-diff::
+ Without this flag, "git log -p <paths>..." shows commits that
+ touch the specified paths, and diffs about the same specified
+ paths. With this, the full diff is shown for commits that touch
+ the specified paths; this means that "<paths>..." limits only
+ commits, and doesn't limit diff for those commits.
<paths>...::
Show only commits that affect the specified paths.
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-read-tree</em> (<tree-ish> | [[-m [--aggressive] | --reset | --prefix=<prefix>] [-u | -i]] [--exclude-per-directory=<gitignore>] [--index-output=<file>] <tree-ish1> [<tree-ish2> [<tree-ish3>]])</p>\r
+<p><em>git-read-tree</em> (<tree-ish> | [[-m [--trivial] [--aggressive] | --reset | --prefix=<prefix>] [-u | -i]] [--exclude-per-directory=<gitignore>] [--index-output=<file>] <tree-ish1> [<tree-ish2> [<tree-ish3>]])</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
</p>\r
</dd>\r
<dt>\r
+--trivial\r
+</dt>\r
+<dd>\r
+<p>\r
+ Restrict three-way merge by <tt>git-read-tree</tt> to happen\r
+ only if there is no file-level merging required, instead\r
+ of resolving merge for trivial cases and leaving\r
+ conflicting files unresolved in the index.\r
+</p>\r
+</dd>\r
+<dt>\r
--aggressive\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:16 UTC\r
+Last updated 21-Jun-2007 00:34:59 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-read-tree' (<tree-ish> | [[-m [--aggressive] | --reset | --prefix=<prefix>] [-u | -i]] [--exclude-per-directory=<gitignore>] [--index-output=<file>] <tree-ish1> [<tree-ish2> [<tree-ish3>]])
+'git-read-tree' (<tree-ish> | [[-m [--trivial] [--aggressive] | --reset | --prefix=<prefix>] [-u | -i]] [--exclude-per-directory=<gitignore>] [--index-output=<file>] <tree-ish1> [<tree-ish2> [<tree-ish3>]])
DESCRIPTION
trees that are not directly related to the current
working tree status into a temporary index file.
+--trivial::
+ Restrict three-way merge by `git-read-tree` to happen
+ only if there is no file-level merging required, instead
+ of resolving merge for trivial cases and leaving
+ conflicting files unresolved in the index.
+
--aggressive::
Usually a three-way merge by `git-read-tree` resolves
the merge for really trivial cases and leaves other
<div class="sectionbody">\r
<dl>\r
<dt>\r
+--stale-fix\r
+</dt>\r
+<dd>\r
+<p>\r
+ This revamps the logic — the definition of "broken commit"\r
+ becomes: a commit that is not reachable from any of the refs and\r
+ there is a missing object among the commit, tree, or blob\r
+ objects reachable from it that is not reachable from any of the\r
+ refs.\r
+</p>\r
+<p>This computation involves traversing all the reachable objects, i.e. it\r
+has the same cost as <em>git prune</em>. Fortunately, once this is run, we\r
+should not have to ever worry about missing objects, because the current\r
+prune and pack-objects know about reflogs and protect objects referred by\r
+them.</p>\r
+</dd>\r
+<dt>\r
--expire=<time>\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:17 UTC\r
+Last updated 21-Jun-2007 00:35:00 UTC\r
</div>\r
</div>\r
</body>\r
OPTIONS
-------
+--stale-fix::
+ This revamps the logic -- the definition of "broken commit"
+ becomes: a commit that is not reachable from any of the refs and
+ there is a missing object among the commit, tree, or blob
+ objects reachable from it that is not reachable from any of the
+ refs.
++
+This computation involves traversing all the reachable objects, i.e. it
+has the same cost as 'git prune'. Fortunately, once this is run, we
+should not have to ever worry about missing objects, because the current
+prune and pack-objects know about reflogs and protect objects referred by
+them.
+
--expire=<time>::
Entries older than this time are pruned. Without the
option it is taken from configuration `gc.reflogExpire`,
[ --sparse ]\r
[ --no-merges ]\r
[ --remove-empty ]\r
+ [ --full-history ]\r
[ --not ]\r
[ --all ]\r
[ --stdin ]\r
[ --topo-order ]\r
[ --parents ]\r
+ [ --timestamp ]\r
[ --left-right ]\r
[ --cherry-pick ]\r
[ --encoding[=<encoding>] ]\r
</p>\r
</dd>\r
<dt>\r
+--abbrev-commit\r
+</dt>\r
+<dd>\r
+<p>\r
+ Instead of showing the full 40-byte hexadecimal commit object\r
+ name, show only handful hexdigits prefix. Non default number of\r
+ digits can be specified with "--abbrev=<n>" (which also modifies\r
+ diff output, if it is displayed).\r
+</p>\r
+<p>This should make "--pretty=oneline" a whole lot more readable for\r
+people using 80-column terminals.</p>\r
+</dd>\r
+<dt>\r
--encoding[=<encoding>]\r
</dt>\r
<dd>\r
</p>\r
</dd>\r
<dt>\r
+--timestamp\r
+</dt>\r
+<dd>\r
+<p>\r
+ Print the raw commit timestamp.\r
+</p>\r
+</dd>\r
+<dt>\r
--left-right\r
</dt>\r
<dd>\r
</p>\r
</dd>\r
<dt>\r
+--full-history\r
+</dt>\r
+<dd>\r
+<p>\r
+ Show also parts of history irrelevant to current state of a given\r
+ path. This turns off history simplification, which removed merges\r
+ which didn't change anything at all at some child. It will still actually\r
+ simplify away merges that didn't change anything at all into either\r
+ child.\r
+</p>\r
+</dd>\r
+<dt>\r
--no-merges\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:19 UTC\r
+Last updated 21-Jun-2007 00:35:00 UTC\r
</div>\r
</div>\r
</body>\r
[ \--sparse ]
[ \--no-merges ]
[ \--remove-empty ]
+ [ \--full-history ]
[ \--not ]
[ \--all ]
[ \--stdin ]
[ \--topo-order ]
[ \--parents ]
+ [ \--timestamp ]
[ \--left-right ]
[ \--cherry-pick ]
[ \--encoding[=<encoding>] ]
Print the parents of the commit.
+--timestamp::
+ Print the raw commit timestamp.
+
--left-right::
Mark which side of a symmetric diff a commit is reachable from.
Stop when a given path disappears from the tree.
+--full-history::
+
+ Show also parts of history irrelevant to current state of a given
+ path. This turns off history simplification, which removed merges
+ which didn't change anything at all at some child. It will still actually
+ simplify away merges that didn't change anything at all into either
+ child.
+
--no-merges::
Do not print commits with more than one parent.
</p>\r
</dd>\r
<dt>\r
+--is-inside-git-dir\r
+</dt>\r
+<dd>\r
+<p>\r
+ Return "true" if we are in the git directory, otherwise "false".\r
+ Some commands require to be run in a working directory.\r
+</p>\r
+</dd>\r
+<dt>\r
--short, --short=number\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:20 UTC\r
+Last updated 21-Jun-2007 00:35:00 UTC\r
</div>\r
</div>\r
</body>\r
--git-dir::
Show `$GIT_DIR` if defined else show the path to the .git directory.
+--is-inside-git-dir::
+ Return "true" if we are in the git directory, otherwise "false".
+ Some commands require to be run in a working directory.
+
--short, --short=number::
Instead of outputting the full SHA1 values of object names try to
abbreviate them to a shorter unique name. When no length is specified
</p>\r
</dd>\r
<dt>\r
+--abbrev-commit\r
+</dt>\r
+<dd>\r
+<p>\r
+ Instead of showing the full 40-byte hexadecimal commit object\r
+ name, show only handful hexdigits prefix. Non default number of\r
+ digits can be specified with "--abbrev=<n>" (which also modifies\r
+ diff output, if it is displayed).\r
+</p>\r
+<p>This should make "--pretty=oneline" a whole lot more readable for\r
+people using 80-column terminals.</p>\r
+</dd>\r
+<dt>\r
--encoding[=<encoding>]\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:22 UTC\r
+Last updated 21-Jun-2007 00:35:01 UTC\r
</div>\r
</div>\r
</body>\r
'full', 'fuller', 'email', 'raw' and 'format:<string>'.
When left out the format default to 'medium'.
+--abbrev-commit::
+ Instead of showing the full 40-byte hexadecimal commit object
+ name, show only handful hexdigits prefix. Non default number of
+ digits can be specified with "--abbrev=<n>" (which also modifies
+ diff output, if it is displayed).
++
+This should make "--pretty=oneline" a whole lot more readable for
+people using 80-column terminals.
+
--encoding[=<encoding>]::
The commit objects record the encoding used for the log message
in their encoding header; this option can be used to tell the