summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 5b98d9b)
raw | patch | inline | side by side (parent: 5b98d9b)
author | J. Bruce Fields <bfields@citi.umich.edu> | |
Mon, 19 Nov 2007 01:50:57 +0000 (20:50 -0500) | ||
committer | J. Bruce Fields <bfields@citi.umich.edu> | |
Mon, 19 Nov 2007 01:50:57 +0000 (20:50 -0500) |
... by changing git-tar-tree reference to git-archive and removing
seemingly unrelevant footnote about git-ssh-{fetch,upload}.
Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
seemingly unrelevant footnote about git-ssh-{fetch,upload}.
Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Documentation/core-tutorial.txt | patch | blob | history | |
Documentation/git-get-tar-commit-id.txt | patch | blob | history |
index c126038c1f289c44e5e65bd03f797e11f3353333..c3f0be535d283266492eb21164dc2f243d97b631 100644 (file)
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 not used by `git pull` or `git push` scripts.
Once you fetch from the remote repository, you `merge` that
with your current branch.
index 9b5f86fc30aecc5e1183e514d5d0f81d14a751c3..60d1c52f449ec9e37c2f3d02bc79aa98af86a325 100644 (file)
NAME
----
-git-get-tar-commit-id - Extract commit ID from an archive created using git-tar-tree
+git-get-tar-commit-id - Extract commit ID from an archive created using git-archive
SYNOPSIS
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 first parameter of git-archive had been
a tree ID instead of a commit ID or tag.