diff options
| author | René Scharfe <rene.scharfe@lsrfire.ath.cx> | 2007-01-17 16:32:41 +0100 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2007-01-17 08:44:32 -0800 |
| commit | 23bfbb815d7d71ff20c014f4610732597f0a75db (patch) | |
| tree | 69a5f28bb990dfb8f5871972c1bac4c9ab0e3cb6 /Documentation/git-blame.txt | |
| parent | 850844e28f728625ba96b7880a0a264a5578e4c6 (diff) | |
| download | git-23bfbb815d7d71ff20c014f4610732597f0a75db.tar.gz | |
Documentation: a few spelling fixes
Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/git-blame.txt')
| -rw-r--r-- | Documentation/git-blame.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt index bdfc666928..b14e794077 100644 --- a/Documentation/git-blame.txt +++ b/Documentation/git-blame.txt @@ -24,7 +24,7 @@ replaced; you need to use a tool such as gitlink:git-diff[1] or the "pickaxe" interface briefly mentioned in the following paragraph. Apart from supporting file annotation, git also supports searching the -development history for when a code snippet occured in a change. This makes it +development history for when a code snippet occurred in a change. This makes it possible to track when a code snippet was added to a file, moved or copied between files, and eventually deleted or replaced. It works by searching for a text string in the diff. A small example: @@ -89,7 +89,7 @@ THE PORCELAIN FORMAT -------------------- In this format, each line is output after a header; the -header at the minumum has the first line which has: +header at the minimum has the first line which has: - 40-byte SHA-1 of the commit the line is attributed to; - the line number of the line in the original file; @@ -112,8 +112,8 @@ header, prefixed by a TAB. This is to allow adding more header elements later. -SPECIFIYING RANGES ------------------- +SPECIFYING RANGES +----------------- Unlike `git-blame` and `git-annotate` in older git, the extent of annotation can be limited to both line ranges and revision |