diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2006-01-06 17:13:58 -0800 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2006-01-06 17:13:58 -0800 |
| commit | 235a91e6b0d1d18a2517cf7e0a18278a6912bdb0 (patch) | |
| tree | 526cd006cb2571a64bb543fbe7fbdd8e425af718 /git-diff-index.txt | |
| parent | ab0087622a692f2980ae9f169beb4459f36bf230 (diff) | |
| download | git-htmldocs-235a91e6b0d1d18a2517cf7e0a18278a6912bdb0.tar.gz | |
Autogenerated HTML docs for 026351a03507dc3a2e89e068c01234dc55914df2
Diffstat (limited to 'git-diff-index.txt')
| -rw-r--r-- | git-diff-index.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/git-diff-index.txt b/git-diff-index.txt index dba6d30fc..5d2096a4c 100644 --- a/git-diff-index.txt +++ b/git-diff-index.txt @@ -53,7 +53,7 @@ If '--cached' is specified, it allows you to ask: contents (the ones I'd write with a "git-write-tree") For example, let's say that you have worked on your working directory, updated -some files in the index and are ready to commit. You want to see eactly +some files in the index and are ready to commit. You want to see exactly *what* you are going to commit is without having to write a new tree object and compare it that way, and to do that, you just do @@ -110,7 +110,7 @@ NOTE: As with other commands of this type, "git-diff-index" does not actually look at the contents of the file at all. So maybe `kernel/sched.c` hasn't actually changed, and it's just that you touched it. In either case, it's a note that you need to -"git-upate-index" it to make the index be in sync. +"git-update-index" it to make the index be in sync. NOTE: You can have a mixture of files show up as "has been updated" and "is still dirty in the working directory" together. You can always |