summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: bebc5c6)
raw | patch | inline | side by side (parent: bebc5c6)
author | Petr Baudis <pasky@ucw.cz> | |
Wed, 11 May 2005 00:15:14 +0000 (02:15 +0200) | ||
committer | Petr Baudis <xpasky@machine.sinus.cz> | |
Wed, 11 May 2005 00:15:14 +0000 (02:15 +0200) |
Two other README spelling fixes. I wasn't able to pinpoint the relevant
commit in the cogito branch, but they are fairly trivial anyway.
commit in the cogito branch, but they are fairly trivial anyway.
README | patch | blob | history |
index 916d43ed4f4b93b2b109aa4249dbea079380c92e..f23eca890ea5bb75de15538cc00801fe71c1dd7e 100644 (file)
--- a/README
+++ b/README
but to avoid common mistakes with filename globbing etc, the
command will not normally add totally new entries or remove old
- entries, i.e. it will normally just update existing cache entryes.
+ entries, i.e. it will normally just update existing cache entries.
To tell git that yes, you really do realize that certain files
no longer exist in the archive, or that new files should be
As a special case, you can also do "update-cache --refresh",
which will refresh the "stat" information of each index to match
the current stat information. It will _not_ update the object
- status itself, and it wil only update the fields that are used
+ status itself, and it will only update the fields that are used
to quickly test whether an object still matches its old backing
store object.