that does not even support directory index would suffice. But\r
you must prepare your repository with <tt>git-update-server-info</tt>\r
to help dumb transport downloaders.</p>\r
-<p>There are (confusingly enough) <tt>git-ssh-fetch</tt> and <tt>git-ssh-upload</tt>\r
-programs, which are <em>commit walkers</em>; they outlived their\r
-usefulness when git Native and SSH transports were introduced,\r
-and are not used by <tt>git pull</tt> or <tt>git push</tt> scripts.</p>\r
</dd>\r
</dl>\r
<p>Once you fetch from the remote repository, you <tt>merge</tt> that\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 10-Nov-2007 11:26:14 UTC\r
+Last updated 13-Nov-2007 08:20:50 UTC\r
</div>\r
</div>\r
</body>\r
that does not even support directory index would suffice. But
you must prepare your repository with `git-update-server-info`
to help dumb transport downloaders.
-+
-There are (confusingly enough) `git-ssh-fetch` and `git-ssh-upload`
-programs, which are 'commit walkers'; they outlived their
-usefulness when git Native and SSH transports were introduced,
-and are not used by `git pull` or `git push` scripts.
Once you fetch from the remote repository, you `merge` that
with your current branch.
</dt>\r
<dd>\r
<p>\r
- When -b is given and a branch is created off a remote branch,\r
+ When a branch is created off a remote branch,\r
set up configuration so that git-pull will not retrieve data\r
from the remote branch, ignoring the branch.autosetupmerge\r
configuration variable.\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 03-Nov-2007 02:45:07 UTC\r
+Last updated 13-Nov-2007 08:20:50 UTC\r
</div>\r
</div>\r
</body>\r
'--track' were given.
--no-track::
- When -b is given and a branch is created off a remote branch,
+ When a branch is created off a remote branch,
set up configuration so that git-pull will not retrieve data
from the remote branch, ignoring the branch.autosetupmerge
configuration variable.
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
<p>Acts as a filter, extracting the commit ID stored in archives created by\r
-git-tar-tree. It reads only the first 1024 bytes of input, thus its\r
+<a href="git-archive.html">git-archive(1)</a>. It reads only the first 1024 bytes of input, thus its\r
runtime is not influenced by the size of <tarfile> very much.</p>\r
<p>If no commit ID is found, git-get-tar-commit-id quietly exists with a\r
return code of 1. This can happen if <tarfile> had not been created\r
-using git-tar-tree or if the first parameter of git-tar-tree had been\r
+using git-archive or if the <treeish> parameter of git-archive had been\r
a tree ID instead of a commit ID or tag.</p>\r
</div>\r
<h2>Author</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:42 UTC\r
+Last updated 13-Nov-2007 08:20:50 UTC\r
</div>\r
</div>\r
</body>\r
DESCRIPTION
-----------
Acts as a filter, extracting the commit ID stored in archives created by
-git-tar-tree. It reads only the first 1024 bytes of input, thus its
+gitlink:git-archive[1]. It reads only the first 1024 bytes of input, thus its
runtime is not influenced by the size of <tarfile> very much.
If no commit ID is found, git-get-tar-commit-id quietly exists with a
return code of 1. This can happen if <tarfile> had not been created
-using git-tar-tree or if the first parameter of git-tar-tree had been
+using git-archive or if the <treeish> parameter of git-archive had been
a tree ID instead of a commit ID or tag.