From: Bo Yang <struggleyb.nku@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Jens.Lehmann@web.de, trast@student.ethz.ch
Subject: [PATCH v2 13/13] some document update
Date: Wed, 30 Jun 2010 23:25:26 +0800 [thread overview]
Message-ID: <1277911526-12105-13-git-send-email-struggleyb.nku@gmail.com> (raw)
In-Reply-To: <1277911526-12105-1-git-send-email-struggleyb.nku@gmail.com>
Signed-off-by: Bo Yang <struggleyb.nku@gmail.com>
---
Documentation/git-log.txt | 30 ++++++++++++++++++++++++++++++
1 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 0e6ff31..14a9703 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -9,6 +9,7 @@ git-log - Show commit logs
SYNOPSIS
--------
'git log' [<options>] [<since>..<until>] [[\--] <path>...]
+'git log' [<options>] -L n,m <path>
DESCRIPTION
-----------
@@ -19,6 +20,9 @@ command to control what is shown and how, and options applicable to
the 'git diff-*' commands to control how the changes
each commit introduces are shown.
+With '-L' option, the command will help to trace the history of user specified
+line ranges. It can trace multiple ranges coming from multiple files.
+
OPTIONS
-------
@@ -72,6 +76,32 @@ include::diff-options.txt[]
to be prefixed with "\-- " to separate them from options or
refnames.
+-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>.
++
+
+--always-print::
+ Always print the interesting range even if the current commit
+ does not change any line of the range.
+
include::rev-list-options.txt[]
--
1.7.0.2.273.gc2413.dirty
next prev parent reply other threads:[~2010-06-30 15:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 15:25 [PATCH v2 01/13] parse-options: stop when encounter a non-option Bo Yang
2010-06-30 15:25 ` [PATCH v2 02/13] parse-options: add two helper functions Bo Yang
2010-06-30 15:25 ` [PATCH v2 03/13] add the basic data structure for line level history Bo Yang
2010-07-06 2:36 ` Junio C Hamano
2010-07-06 14:21 ` Bo Yang
2010-06-30 15:25 ` [PATCH v2 04/13] refactor parse_loc Bo Yang
2010-06-30 15:25 ` [PATCH v2 05/13] parse the -L options Bo Yang
2010-06-30 15:25 ` [PATCH v2 06/13] export three functions from diff.c Bo Yang
2010-06-30 15:25 ` [PATCH v2 07/13] add range clone functions Bo Yang
2010-06-30 15:25 ` [PATCH v2 08/13] map/take range to parent Bo Yang
2010-06-30 15:25 ` [PATCH v2 09/13] print the line log Bo Yang
2010-06-30 15:25 ` [PATCH v2 10/13] map/print ranges along traversing the history topologically Bo Yang
2010-06-30 15:25 ` [PATCH v2 11/13] add --always-print option Bo Yang
2010-06-30 15:25 ` [PATCH v2 12/13] add two test cases Bo Yang
2010-06-30 15:25 ` Bo Yang [this message]
2010-07-06 2:36 ` [PATCH v2 01/13] parse-options: stop when encounter a non-option Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1277911526-12105-13-git-send-email-struggleyb.nku@gmail.com \
--to=struggleyb.nku@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@student.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).