-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improve the formatting of the description of the line-range option '-L' for `git log`, `gitk` and `git blame`: - Use bold for <start>, <end> and <funcname> - Use backticks for literals Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
- Loading branch information
1 parent
f9c8d8c
commit fd5c74e
Showing
3 changed files
with
17 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,30 +1,30 @@ | ||
<start> and <end> can take one of these forms: | ||
'<start>' and '<end>' can take one of these forms: | ||
|
||
- number | ||
+ | ||
If <start> or <end> is a number, it specifies an | ||
If '<start>' or '<end>' is a number, it specifies an | ||
absolute line number (lines count from 1). | ||
+ | ||
|
||
- /regex/ | ||
- `/regex/` | ||
+ | ||
This form will use the first line matching the given | ||
POSIX regex. If <start> is a regex, it will search from the end of | ||
POSIX regex. If '<start>' is a regex, it will search from the end of | ||
the previous `-L` range, if any, otherwise from the start of file. | ||
If <start> is ``^/regex/'', it will search from the start of file. | ||
If <end> is a regex, it will search | ||
starting at the line given by <start>. | ||
If '<start>' is `^/regex/`, it will search from the start of file. | ||
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>. | ||
This is only valid for '<end>' and will specify a number | ||
of lines before or after the line given by '<start>'. | ||
|
||
+ | ||
If ``:<funcname>'' is given in place of <start> and <end>, it is a | ||
If `:<funcname>` is given in place of '<start>' and '<end>', it is a | ||
regular expression that denotes the range from the first funcname line | ||
that matches <funcname>, up to the next funcname line. ``:<funcname>'' | ||
that matches '<funcname>', up to the next funcname line. `:<funcname>` | ||
searches from the end of the previous `-L` range, if any, otherwise | ||
from the start of file. ``^:<funcname>'' searches from the start of | ||
from the start of file. `^:<funcname>` searches from the start of | ||
file. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters