summaryrefslogtreecommitdiffstats
path: root/git-blame.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2007-01-17 17:42:30 +0000
committerJunio C Hamano <junio@hera.kernel.org>2007-01-17 17:42:30 +0000
commitf9771f69968326f60eaa1b69efe27a302998c755 (patch)
tree14f148fe4a54b0f8dfccc83b7dbd37034216d385 /git-blame.txt
parent8f76dc6fae3bb5536b36c987aa521322dcdd220c (diff)
downloadgit-htmldocs-f9771f69968326f60eaa1b69efe27a302998c755.tar.gz
Autogenerated HTML docs for v1.5.0-rc1-g23bf
Diffstat (limited to 'git-blame.txt')
-rw-r--r--git-blame.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/git-blame.txt b/git-blame.txt
index bdfc66692..b14e79407 100644
--- a/git-blame.txt
+++ b/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