From a7154e916c6fab01dfb67629dae8c4430daff669 Mon Sep 17 00:00:00 2001 From: Sergey Vlasov Date: Mon, 19 Sep 2005 14:10:51 +0400 Subject: [PATCH] Documentation: Update all files to use the new gitlink: macro The replacement was performed automatically by these commands: perl -pi -e 's/link:(git.+)\.html\[\1\]/gitlink:$1\[1\]/g' \ README Documentation/*.txt perl -pi -e 's/link:git\.html\[git\]/gitlink:git\[7\]/g' \ README Documentation/*.txt Signed-off-by: Sergey Vlasov Signed-off-by: Junio C Hamano --- README | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'README') diff --git a/README b/README index 6b38a7aa7..0ee49d489 100644 --- a/README +++ b/README @@ -104,8 +104,8 @@ object. The object is totally independent of its location in the directory tree, and renaming a file does not change the object that file is associated with in any way. -A blob is typically created when link:git-update-index.html[git-update-index] -is run, and its data can be accessed by link:git-cat-file.html[git-cat-file]. +A blob is typically created when gitlink:git-update-index[1] +is run, and its data can be accessed by gitlink:git-cat-file[1]. Tree Object ~~~~~~~~~~~ @@ -143,9 +143,9 @@ involved), you can see trivial renames or permission changes by noticing that the blob stayed the same. However, renames with data changes need a smarter "diff" implementation. -A tree is created with link:git-write-tree.html[git-write-tree] and -its data can be accessed by link:git-ls-tree.html[git-ls-tree]. -Two trees can be compared with link:git-diff-tree.html[git-diff-tree]. +A tree is created with gitlink:git-write-tree[1] and +its data can be accessed by gitlink:git-ls-tree[1]. +Two trees can be compared with gitlink:git-diff-tree[1]. Commit Object ~~~~~~~~~~~~~ @@ -169,8 +169,8 @@ implicit in the trees involved (the result tree, and the result trees of the parents), and describing that makes no sense in this idiotic file manager. -A commit is created with link:git-commit-tree.html[git-commit-tree] and -its data can be accessed by link:git-cat-file.html[git-cat-file]. +A commit is created with gitlink:git-commit-tree[1] and +its data can be accessed by gitlink:git-cat-file[1]. Trust ~~~~~ @@ -215,10 +215,10 @@ Note that despite the tag features, "git" itself only handles content integrity; the trust framework (and signature provision and verification) has to come from outside. -A tag is created with link:git-mktag.html[git-mktag], -its data can be accessed by link:git-cat-file.html[git-cat-file], +A tag is created with gitlink:git-mktag[1], +its data can be accessed by gitlink:git-cat-file[1], and the signature can be verified by -link:git-verify-tag.html[git-verify-tag]. +gitlink:git-verify-tag[1]. The "index" aka "Current Directory Cache" @@ -286,7 +286,7 @@ main combinations: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You update the index with information from the working directory with -the link:git-update-index.html[git-update-index] command. You +the gitlink:git-update-index[1] command. You generally update the index information by just specifying the filename you want to update, like so: @@ -404,7 +404,7 @@ last committed state was. You can examine the data represented in the object database and the index with various helper tools. For every object, you can use -link:git-cat-file.html[git-cat-file] to examine details about the +gitlink:git-cat-file[1] to examine details about the object: git-cat-file -t -- cgit v1.2.1