Bo Yang <struggleyb.nku@xxxxxxxxx> writes: > Documentation/git-log.txt | 30 ++++++++++++++++++++++++++++++ > 1 files changed, 30 insertions(+), 0 deletions(-) [...] > +-L <start>,<end>:: > + The line range. <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 <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 the parsing code for -L <start>,<end> is the same for git-blame and for git-log, and therefore documentation is the same or nearly the same for this option, wouldn't it be better to separate this documentation into separate file, e.g. line-range-option.txt, and include it both in git-blame and git-log manpages? If there are minor differences, they can be covered by ifdefs. -- Jakub Narebski Poland ShadeHawk on #git -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html