* "git-rebase -interactive" did not handle its "--strategy" option
properly.
-
---
-exec >/var/tmp/1
-O=v1.5.3.4-65-gf91333d
-echo O=`git describe refs/heads/maint`
-git shortlog --no-merges $O..refs/heads/maint
<dd>\r
<p>\r
Create a <em>shallow</em> clone with a history truncated to the\r
- specified number of revs. A shallow repository has\r
+ specified number of revisions. A shallow repository has a\r
number of limitations (you cannot clone or fetch from\r
it, nor push from nor into it), but is adequate if you\r
- want to only look at near the tip of a large project\r
- with a long history, and would want to send in a fixes\r
+ are only interested in the recent history of a large project\r
+ with a long history, and would want to send in fixes\r
as patches.\r
</p>\r
</dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Sep-2007 01:32:39 UTC\r
+Last updated 02-Nov-2007 02:47:20 UTC\r
</div>\r
</div>\r
</body>\r
--depth <depth>::
Create a 'shallow' clone with a history truncated to the
- specified number of revs. A shallow repository has
+ specified number of revisions. A shallow repository has a
number of limitations (you cannot clone or fetch from
it, nor push from nor into it), but is adequate if you
- want to only look at near the tip of a large project
- with a long history, and would want to send in a fixes
+ are only interested in the recent history of a large project
+ with a long history, and would want to send in fixes
as patches.
<repository>::
git commit-tree "$@";\r
fi' HEAD</tt></pre>\r
</div></div>\r
-<p>The function <em>skip_commits</em> is defined as follows:</p>\r
+<p>The function <em>skip_commit</em> is defined as follows:</p>\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt>skip_commit()\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 23-Oct-2007 01:21:48 UTC\r
+Last updated 02-Nov-2007 02:47:20 UTC\r
</div>\r
</div>\r
</body>\r
fi' HEAD
------------------------------------------------------------------------------
-The function 'skip_commits' is defined as follows:
+The function 'skip_commit' is defined as follows:
--------------------------
skip_commit()
</dt>\r
<dd>\r
<p>\r
- Extract all commits which that leads to <em>origin</em> since the\r
+ Extract all commits that lead to <em>origin</em> since the\r
inception of the project.\r
</p>\r
</dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 03-Oct-2007 12:03:48 UTC\r
+Last updated 02-Nov-2007 02:47:21 UTC\r
</div>\r
</div>\r
</body>\r
is created in the current directory.
git-format-patch \--root origin::
- Extract all commits which that leads to 'origin' since the
+ Extract all commits that lead to 'origin' since the
inception of the project.
git-format-patch -M -B origin::
<p>\r
Use the merge resolution program specified by <tool>.\r
Valid merge tools are:\r
- kdiff3, tkdiff, meld, xxdiff, emerge, vimdiff, gvimdiff, and opendiff\r
+ kdiff3, tkdiff, meld, xxdiff, emerge, vimdiff, gvimdiff, ecmerge, and opendiff\r
</p>\r
<p>If a merge resolution program is not specified, <em>git mergetool</em>\r
will use the configuration variable merge.tool. If the\r
configuration variable merge.tool is not set, <em>git mergetool</em>\r
will pick a suitable default.</p>\r
+<p>You can explicitly provide a full path to the tool by setting the\r
+configuration variable mergetool.<tool>.path. For example, you\r
+can configure the absolute path to kdiff3 by setting\r
+mergetool.kdiff3.path. Otherwise, <em>git mergetool</em> assumes the tool\r
+is available in PATH.</p>\r
</dd>\r
</dl>\r
</div>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:46 UTC\r
+Last updated 02-Nov-2007 02:47:21 UTC\r
</div>\r
</div>\r
</body>\r
-t or --tool=<tool>::
Use the merge resolution program specified by <tool>.
Valid merge tools are:
- kdiff3, tkdiff, meld, xxdiff, emerge, vimdiff, gvimdiff, and opendiff
+ kdiff3, tkdiff, meld, xxdiff, emerge, vimdiff, gvimdiff, ecmerge, and opendiff
+
If a merge resolution program is not specified, 'git mergetool'
will use the configuration variable merge.tool. If the
configuration variable merge.tool is not set, 'git mergetool'
will pick a suitable default.
++
+You can explicitly provide a full path to the tool by setting the
+configuration variable mergetool.<tool>.path. For example, you
+can configure the absolute path to kdiff3 by setting
+mergetool.kdiff3.path. Otherwise, 'git mergetool' assumes the tool
+is available in PATH.
Author
------
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 31-Oct-2007 05:56:51 UTC\r
+Last updated 02-Nov-2007 02:47:22 UTC\r
</div>\r
</div>\r
</body>\r
* link:v1.5.3/git.html[documentation for release 1.5.3]
* release notes for
+ link:RelNotes-1.5.3.5.txt[1.5.3.5],
link:RelNotes-1.5.3.4.txt[1.5.3.4],
link:RelNotes-1.5.3.3.txt[1.5.3.3],
link:RelNotes-1.5.3.2.txt[1.5.3.2],