diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-27 09:49:36 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-27 09:49:36 +0000 |
commit | 5ec6074f0633939fd17d94111d10c6c6b062978c (patch) | |
tree | bfaa17b5a64abc66c918e9c70969e519d9e1df8e /Documentation/line-range-format.txt | |
parent | Initial commit. (diff) | |
download | git-5ec6074f0633939fd17d94111d10c6c6b062978c.tar.xz git-5ec6074f0633939fd17d94111d10c6c6b062978c.zip |
Adding upstream version 1:2.30.2.upstream/1%2.30.2upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'Documentation/line-range-format.txt')
-rw-r--r-- | Documentation/line-range-format.txt | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/Documentation/line-range-format.txt b/Documentation/line-range-format.txt new file mode 100644 index 0000000..9b51e9f --- /dev/null +++ b/Documentation/line-range-format.txt @@ -0,0 +1,32 @@ +'<start>' and '<end>' can take one of these forms: + +- 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 '<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>'. ++ + +- +offset or -offset ++ +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 +regular expression that denotes the range from the first funcname line +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 +file. The function names are determined in the same way as `git diff` +works out patch hunk headers (see 'Defining a custom hunk-header' +in linkgit:gitattributes[5]). |