diff options
| author |  Horst H. von Brand <vonbrand@inf.utfsm.cl> | 2006-06-03 16:27:26 -0400 |
|---|---|---|
| committer |  Junio C Hamano <junkio@cox.net> | 2006-06-03 23:54:55 -0700 |
| commit | abda1ef590d94a5e15e7ce3b685b5c092a790cfa (patch) | |
| tree | 73162a92b2abd5d87b86566899e321dd8ccef59c /Documentation/git-fsck-objects.txt | |
| parent | Builtin git-rev-parse. (diff) | |
| download | tgif-abda1ef590d94a5e15e7ce3b685b5c092a790cfa.tar.xz | |
Documentation: Spelling fixes
Signed-off-by: Horst H. von Brand <vonbrand@inf.utfsm.cl>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/git-fsck-objects.txt')
| -rw-r--r-- | Documentation/git-fsck-objects.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-fsck-objects.txt b/Documentation/git-fsck-objects.txt index 93ce9dcc92..d0af99d351 100644 --- a/Documentation/git-fsck-objects.txt +++ b/Documentation/git-fsck-objects.txt @@ -71,7 +71,7 @@ sorted properly etc), but on the whole if "git-fsck-objects" is happy, you do have a valid tree. Any corrupt objects you will have to find in backups or other archives -(ie you can just remove them and do an "rsync" with some other site in +(i.e., you can just remove them and do an "rsync" with some other site in the hopes that somebody else has the object you have corrupted). Of course, "valid tree" doesn't mean that it wasn't generated by some |