git-commit-vandalism/Documentation/line-range-format.txt

- number
+
If <start> or <end> is a number, it specifies an
absolute line number (lines count from 1).
+

- /regex/
+
This form will use the first line matching the given
POSIX regex.  If <end> is a regex, it will search
starting at the line given by <start>.
+

- +offset or -offset
+
This is only valid for <end> and will specify a number
of lines before or after the line given by <start>.
+

- :regex
+
If the option's argument is of the form :regex, it denotes the range
from the first funcname line that matches <regex>, up to the next
funcname line.
+
Refactor parse_loc We want to use the same style of -L n,m argument for 'git log -L' as for git-blame. Refactor the argument parsing of the range arguments from builtin/blame.c to the (new) file that will hold the 'git log -L' logic. To accommodate different data structures in blame and log -L, the file contents are abstracted away; parse_range_arg takes a callback that it uses to get the contents of a line of the (notional) file. The new test is for a case that made me pause during debugging: the 'blame -L with invalid end' test was the only one that noticed an outright failure to parse the end at all. So make a more explicit test for that. Signed-off-by: Bo Yang <struggleyb.nku@gmail.com> Signed-off-by: Thomas Rast <trast@student.ethz.ch> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2013-03-28 17:47:30 +01:00			`- number`
			`+`
			`If <start> or <end> is a number, it specifies an`
			`absolute line number (lines count from 1).`
			`+`

			`- /regex/`
			`+`
			`This form will use the first line matching the given`
			`POSIX regex. If <end> is a regex, it will search`
			`starting at the line given by <start>.`
			`+`

			`- +offset or -offset`
			`+`
			`This is only valid for <end> and will specify a number`
			`of lines before or after the line given by <start>.`
			`+`
log -L: :pattern:file syntax to find by funcname This new syntax finds a funcname matching /pattern/, and then takes from there up to (but not including) the next funcname. So you can say git log -L:main:main.c and it will dig up the main() function and show its line-log, provided there are no other funcnames matching 'main'. Signed-off-by: Thomas Rast <trast@student.ethz.ch> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2013-03-28 17:47:33 +01:00
			`- :regex`
			`+`
			`If the option's argument is of the form :regex, it denotes the range`
			`from the first funcname line that matches <regex>, up to the next`
			`funcname line.`
			`+`