diff options
| author | Petr Baudis <pasky@ucw.cz> | 2005-05-11 02:15:14 +0200 |
|---|---|---|
| committer | Petr Baudis <xpasky@machine.sinus.cz> | 2005-05-11 02:15:14 +0200 |
| commit | f7ec43ae2257241ef76a69d9d3df031a181f6ebb (patch) | |
| tree | e54e21c1b44d3247940c5ba6e5d743f82f100345 /README | |
| parent | bebc5c61439a291e8f0f99e037ebdf63d3dfac46 (diff) | |
| download | git-f7ec43ae2257241ef76a69d9d3df031a181f6ebb.tar.gz | |
More README spelling fixes
Two other README spelling fixes. I wasn't able to pinpoint the relevant
commit in the cogito branch, but they are fairly trivial anyway.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -265,7 +265,7 @@ main combinations: 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 @@ -283,7 +283,7 @@ main combinations: 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. |