</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
+<p>This is usually not what an end user wants to run directly. See\r
+<a href="git-am.html">git-am(1)</a> instead.</p>\r
<p>Takes three files <msg>, <patch>, and <info> prepared from an\r
e-mail message by <em>git-mailinfo</em>, and creates a commit. It is\r
usually not necessary to use this command directly.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 03-Oct-2006 08:40:51 UTC\r
+Last updated 17-Jan-2007 23:27:37 UTC\r
</div>\r
</div>\r
</body>\r
DESCRIPTION
-----------
+This is usually not what an end user wants to run directly. See
+gitlink:git-am[1] instead.
+
Takes three files <msg>, <patch>, and <info> prepared from an
e-mail message by 'git-mailinfo', and creates a commit. It is
usually not necessary to use this command directly.
<p>Unlike <tt>git-blame</tt> and <tt>git-annotate</tt> in older git, the extent\r
of annotation can be limited to both line ranges and revision\r
ranges. When you are interested in finding the origin for\r
-ll. 40-60 for file <tt>foo</tt>, you can use <tt>-L</tt> option like this:</p>\r
+ll. 40-60 for file <tt>foo</tt>, you can use <tt>-L</tt> option like these\r
+(they mean the same thing — both ask for 21 lines starting at\r
+line 40):</p>\r
<div class="literalblock">\r
<div class="content">\r
-<pre><tt>git blame -L 40,60 foo</tt></pre>\r
+<pre><tt>git blame -L 40,60 foo\r
+git blame -L 40,+21 foo</tt></pre>\r
</div></div>\r
<p>Also you can use regular expression to specify the line range.</p>\r
<div class="literalblock">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 17-Jan-2007 17:42:11 UTC\r
+Last updated 17-Jan-2007 23:27:38 UTC\r
</div>\r
</div>\r
</body>\r
Unlike `git-blame` and `git-annotate` in older git, the extent
of annotation can be limited to both line ranges and revision
ranges. When you are interested in finding the origin for
-ll. 40-60 for file `foo`, you can use `-L` option like this:
+ll. 40-60 for file `foo`, you can use `-L` option like these
+(they mean the same thing -- both ask for 21 lines starting at
+line 40):
git blame -L 40,60 foo
+ git blame -L 40,+21 foo
Also you can use regular expression to specify the line range.
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
+<p>This is usually not what an end user wants to run directly. See\r
+<a href="git-commit.html">git-commit(1)</a> instead.</p>\r
<p>Creates a new commit object based on the provided tree object and\r
emits the new commit object id on stdout. If no parent is given then\r
it is considered to be an initial tree.</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 31-Dec-2006 01:19:01 UTC\r
+Last updated 17-Jan-2007 23:27:38 UTC\r
</div>\r
</div>\r
</body>\r
DESCRIPTION
-----------
+This is usually not what an end user wants to run directly. See
+gitlink:git-commit[1] instead.
+
Creates a new commit object based on the provided tree object and
emits the new commit object id on stdout. If no parent is given then
it is considered to be an initial tree.
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
+<p>Usually you would want to use <a href="git-fetch.html">git-fetch(1)</a> which is a\r
+higher level wrapper of this command instead.</p>\r
<p>Invokes <em>git-upload-pack</em> on a potentially remote repository,\r
and asks it to send objects missing from this repository, to\r
update the named heads. The list of commits available locally\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 08-Nov-2006 01:33:27 UTC\r
+Last updated 17-Jan-2007 23:27:39 UTC\r
</div>\r
</div>\r
</body>\r
DESCRIPTION
-----------
+Usually you would want to use gitlink:git-fetch[1] which is a
+higher level wrapper of this command instead.
+
Invokes 'git-upload-pack' on a potentially remote repository,
and asks it to send objects missing from this repository, to
update the named heads. The list of commits available locally
<patch> file. The author name, e-mail and e-mail subject are\r
written out to the standard output to be used by git-applypatch\r
to create a commit. It is usually not necessary to use this\r
-command directly.</p>\r
+command directly. See <a href="git-am.html">git-am(1)</a> instead.</p>\r
</div>\r
<h2>OPTIONS</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Jan-2007 05:37:42 UTC\r
+Last updated 17-Jan-2007 23:27:39 UTC\r
</div>\r
</div>\r
</body>\r
<patch> file. The author name, e-mail and e-mail subject are
written out to the standard output to be used by git-applypatch
to create a commit. It is usually not necessary to use this
-command directly.
+command directly. See gitlink:git-am[1] instead.
OPTIONS
<div class="sectionbody">\r
<p>This script is included in various scripts to supply\r
routines to parse files under $GIT_DIR/remotes/ and\r
-$GIT_DIR/branches/.</p>\r
+$GIT_DIR/branches/ and configuration variables that are related\r
+to fetching, pulling and pushing.</p>\r
<p>The primary entry points are:</p>\r
<dl>\r
<dt>\r
(e.g. <tt>refs/heads/foo</tt>). When <tt><refspec>…</tt> is empty\r
the returned list of refs consists of the defaults\r
for the given <tt><repo></tt>, if specified in\r
- <tt>$GIT_DIR/remotes/</tt> or <tt>$GIT_DIR/branches/</tt>.\r
+ <tt>$GIT_DIR/remotes/</tt>, <tt>$GIT_DIR/branches/</tt>, or <tt>remote.*.fetch</tt>\r
+ configuration.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 03-Oct-2006 08:41:16 UTC\r
+Last updated 17-Jan-2007 23:27:40 UTC\r
</div>\r
</div>\r
</body>\r
-----------
This script is included in various scripts to supply
routines to parse files under $GIT_DIR/remotes/ and
-$GIT_DIR/branches/.
+$GIT_DIR/branches/ and configuration variables that are related
+to fetching, pulling and pushing.
The primary entry points are:
(e.g. `refs/heads/foo`). When `<refspec>...` is empty
the returned list of refs consists of the defaults
for the given `<repo>`, if specified in
- `$GIT_DIR/remotes/` or `$GIT_DIR/branches/`.
+ `$GIT_DIR/remotes/`, `$GIT_DIR/branches/`, or `remote.*.fetch`
+ configuration.
get_remote_refs_for_push::
Given the list of user-supplied `<repo> <refspec>...`,
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
+<p>DEPRECATED. Use <tt>git-merge</tt> instead.</p>\r
<p>Given two commits and a merge message, merge the <merged> commit\r
into <current> commit, with the commit log message <message>.</p>\r
<p>When <current> is a descendant of <merged>, or <current> is an\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 03-Oct-2006 08:41:24 UTC\r
+Last updated 17-Jan-2007 23:27:40 UTC\r
</div>\r
</div>\r
</body>\r
DESCRIPTION
-----------
+DEPRECATED. Use `git-merge` instead.
+
Given two commits and a merge message, merge the <merged> commit
into <current> commit, with the commit log message <message>.
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
+<p>Usually you would want to use <a href="git-push.html">git-push(1)</a> which is a\r
+higher level wrapper of this command instead.</p>\r
<p>Invokes <em>git-receive-pack</em> on a possibly remote repository, and\r
updates it from the current repository, sending named refs.</p>\r
</div>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 12-Oct-2006 19:10:26 UTC\r
+Last updated 17-Jan-2007 23:27:40 UTC\r
</div>\r
</div>\r
</body>\r
DESCRIPTION
-----------
+Usually you would want to use gitlink:git-push[1] which is a
+higher level wrapper of this command instead.
+
Invokes 'git-receive-pack' on a possibly remote repository, and
updates it from the current repository, sending named refs.
projects / git.git / commitdiff