summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 90c4851)
raw | patch | inline | side by side (parent: 90c4851)
author | Zack Brown <zbrown@tumblerings.org> | |
Mon, 25 Apr 2005 21:28:33 +0000 (14:28 -0700) | ||
committer | Petr Baudis <xpasky@machine.sinus.cz> | |
Wed, 11 May 2005 00:08:53 +0000 (02:08 +0200) |
Signed-off-by: Zack Brown <zbrown@tumblerings.org>
Signed-off-by: Petr Baudis <pasky@ucw.cz>
Signed-off-by: Petr Baudis <pasky@ucw.cz>
README | patch | blob | history |
index 250093063f5703f3ab02251de513d6203bf7f414..916d43ed4f4b93b2b109aa4249dbea079380c92e 100644 (file)
--- a/README
+++ b/README
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 toally independent
+ share the same blob object. The object is totally independent
of it's location in the directory tree, and renaming a file does
not change the object that file is associated with in any way.
changes in your working directory (i.e. "update-cache").
However, if you decide to jump to a new version, or check out
- somebody elses version, or just restore a previous tree, you'd
+ somebody else's version, or just restore a previous tree, you'd
populate your index file with read-tree, and then you need to
check out the result with