From: Thomas Rast <trast@student.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: [PATCH] Documentation: point to "History Simplification" from -- <path>
Date: Tue, 30 Aug 2011 01:18:19 +0200 [thread overview]
Message-ID: <307fe311ad448ecd3d0643040008954a217d7ddb.1314659821.git.trast@student.ethz.ch> (raw)
'git log -- <path>' does not "show commits that affect the specified
paths" in a literal sense unless --full-history is given (for example,
a file that only existed on a side branch will turn up no commits at
all!).
Point the user to the "History Simplification" section to avoid
surprises.
Signed-off-by: Thomas Rast <trast@student.ethz.ch>
---
Sparked by an IRC discussion minutes ago, where I got the paragraph
quoted back to me verbatim to "prove" it shows *all* commits affecting
a file.
Documentation/git-log.txt | 10 ++++++----
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 6c93466..437f06e 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -69,10 +69,12 @@ produced by --stat etc.
its size is not included.
[\--] <path>...::
- Show only commits that affect any of the specified paths. To
- prevent confusion with options and branch names, paths may need
- to be prefixed with "\-- " to separate them from options or
- refnames.
+ Show only commits that affect any of the specified paths.
+ See "History Simplification" below for a precise definition of
+ the filtering applied.
++
+To prevent confusion with options and branch names, paths may need to
+be prefixed with "\-- " to separate them from options or refnames.
include::rev-list-options.txt[]
--
1.7.7.rc0.370.gdcae57
next reply other threads:[~2011-08-29 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 23:18 Thomas Rast [this message]
2011-08-29 23:50 ` [PATCH] Documentation: point to "History Simplification" from -- <path> Junio C Hamano
2011-08-30 9:21 ` [PATCH v2] Documentation: clarify effects of -- <path> arguments Thomas Rast
2011-08-30 18:03 ` 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=307fe311ad448ecd3d0643040008954a217d7ddb.1314659821.git.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).