@matheusbsbs / matheus-bagliano / commits / a4e57e75c9
Fork 0

Documentation: Fix references to deprecated commands

... 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: Junio C Hamano <gitster@pobox.com>

Jonas Fonseca committed Nov 12, 2007 at 01:32 UTC a4e57e75c95c66c32da6b106313bc847110794ba
2 files changed +2 -7
Documentation/core-tutorial.txt
-5
@@ -1090,11 +1090,6 @@ server like git Native transport does. Any stock HTTP server
1090 that does not even support directory index would suffice. But
1091 you must prepare your repository with `git-update-server-info`
1092 to help dumb transport downloaders.
1093 -+
1094 -There are (confusingly enough) `git-ssh-fetch` and `git-ssh-upload`
1095 -programs, which are 'commit walkers'; they outlived their
1096 -usefulness when git Native and SSH transports were introduced,
1097 -and are not used by `git pull` or `git push` scripts.
1093
1094 Once you fetch from the remote repository, you `merge` that
1095 with your current branch.
Documentation/git-get-tar-commit-id.txt
+2 -2
@@ -14,12 +14,12 @@ SYNOPSIS
14 DESCRIPTION
15 -----------
16 Acts as a filter, extracting the commit ID stored in archives created by
17 -git-tar-tree. It reads only the first 1024 bytes of input, thus its
17 +gitlink:git-archive[1]. It reads only the first 1024 bytes of input, thus its
18 runtime is not influenced by the size of <tarfile> very much.
19
20 If no commit ID is found, git-get-tar-commit-id quietly exists with a
21 return code of 1. This can happen if <tarfile> had not been created
22 -using git-tar-tree or if the first parameter of git-tar-tree had been
22 +using git-archive or if the <treeish> parameter of git-archive had been
23 a tree ID instead of a commit ID or tag.
24
25