sticking with blame for now

schacon · schacon · commit a5f85ba58759 · 2008-09-02T15:30:18.000-07:00
diff --git a/text/28_Finding_Issues_Git_Blame/0_ Finding_Issues_Git_Blame.markdown b/text/28_Finding_Issues_Git_Blame/0_ Finding_Issues_Git_Blame.markdown
@@ -15,15 +15,16 @@ line in the file.
 	8e440259 (Peter Eriksen   2006-04-02 14:44:09 +0200   13) #include "commit.h"
 	8e440259 (Peter Eriksen   2006-04-02 14:44:09 +0200   14) #include "tag.h"
 	8e440259 (Peter Eriksen   2006-04-02 14:44:09 +0200   15) #include "tree.h"
-	f35a6d3b (Linus Torvalds  2007-04-09 21:20:29 -0700   16) #include "refs.h"70f5d5d3 (Nicolas Pitre               2008-02-28 00:25:19 -0500   17) #include "pack-revindex.h"628522ec (Junio C Hamano              2007-12-29 02:05:47 -0800   18) #include "sha1-lookup.h"
+	f35a6d3b (Linus Torvalds  2007-04-09 21:20:29 -0700   16) #include "refs.h"
+	70f5d5d3 (Nicolas Pitre   2008-02-28 00:25:19 -0500   17) #include "pack-revindex.h"628522ec (Junio C Hamano              2007-12-29 02:05:47 -0800   18) #include "sha1-lookup.h"
 	...
 	
 This is often helpful if a file had a line reverted or a mistake that broke 
 the build to help you see who changed that line last.  
 
 You can also specify a start and end line for the blame:
 
-	$>git annotate -L 160,+10 sha1_file.c 
+	$>git blame -L 160,+10 sha1_file.c 
 	ace1534d (Junio C Hamano 2005-05-07 00:38:04 -0700       160)}
 	ace1534d (Junio C Hamano 2005-05-07 00:38:04 -0700       161)
 	0fcfd160 (Linus Torvalds 2005-04-18 13:04:43 -0700       162)/*
