diff options
| author | Greg Louis <glouis@dynamicro.ca> | 2005-08-17 12:37:04 -0400 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2005-08-17 12:13:12 -0700 |
| commit | cdacb6208fdb6779b21350644d61bd90e63db3d5 (patch) | |
| tree | 720d539dcfa6769252b205c40f49c9a2d97e7375 /README | |
| parent | fbfd60d65142848299513dfa6b477d0f5299cc15 (diff) | |
| download | git-cdacb6208fdb6779b21350644d61bd90e63db3d5.tar.gz git-cdacb6208fdb6779b21350644d61bd90e63db3d5.tar.xz | |
[PATCH] use it's and its correctly in documentation
At one place in Documentation/tutorial.txt and several in the base
README, its was wrongly used in place of it's or vice versa. One
instance remains somewhere in Documentation/howto/, which I didn't
correct because it's in a quotation.
Signed-off-by: Greg Louis <glouis@dynamicro.ca>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -98,12 +98,12 @@ contents"). In particular, since the blob is entirely defined by its data, if two files in a directory tree (or in multiple different versions of the repository) have the same contents, they will share the same blob -object. The object is totally independent of it's location in the +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-cache.html[git-update-cache] -is run, and it's data can be accessed by link:git-cat-file.html[git-cat-file]. +is run, and its data can be accessed by link:git-cat-file.html[git-cat-file]. Tree Object ~~~~~~~~~~~ @@ -142,7 +142,7 @@ 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 -it's data can be accessed by link:git-ls-tree.html[git-ls-tree] +its data can be accessed by link:git-ls-tree.html[git-ls-tree] Commit Object ~~~~~~~~~~~~~ @@ -167,7 +167,7 @@ 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 -it's data can be accessed by link:git-cat-file.html[git-cat-file] +its data can be accessed by link:git-cat-file.html[git-cat-file] Trust ~~~~~ @@ -213,7 +213,7 @@ 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] and -it's data can be accessed by link:git-cat-file.html[git-cat-file] +its data can be accessed by link:git-cat-file.html[git-cat-file] The "index" aka "Current Directory Cache" |