From: Miklos Vajna <vmiklos@frugalware.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Miklos Vajna <vmiklos@frugalware.org>, git@vger.kernel.org
Subject: [PATCH] Include diff options in the git-log manpage
Date: Thu, 1 Nov 2007 15:57:40 +0100 [thread overview]
Message-ID: <1193929060-6183-2-git-send-email-vmiklos@frugalware.org> (raw)
In-Reply-To: <1193929060-6183-1-git-send-email-vmiklos@frugalware.org>
Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
---
Recently I wanted to see what git log -M does but actually I was not able to
find it in the manpage, finally figured out that all the diff options are
missing from here.
Removing -p as it's already in diff-options.txt.
If this patch OK, then I would like to send a similar patch to
git-rev-list.txt, too.
Documentation/git-log.txt | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 5ec547c..4b1b982 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -27,6 +27,8 @@ OPTIONS
include::pretty-options.txt[]
+include::diff-options.txt[]
+
-<n>::
Limits the number of commits to show.
@@ -43,9 +45,6 @@ include::pretty-options.txt[]
commit. This option gives a better overview of the
evolution of a particular branch.
--p::
- Show the change the commit introduces in a patch form.
-
-g, \--walk-reflogs::
Show commits as they were recorded in the reflog. The log contains
a record about how the tip of a reference was changed.
--
1.5.3.5
next prev parent reply other threads:[~2007-11-01 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 14:57 [PATCH] Document that using -M without other diff options is not a good idea Miklos Vajna
2007-11-01 14:57 ` Miklos Vajna [this message]
2007-11-12 15:37 ` [PATCH] Include diff options in the git-log manpage Miklos Vajna
2007-12-04 12:28 ` Miklos Vajna
2007-12-04 17:57 ` Junio C Hamano
2007-12-05 6:45 ` Junio C Hamano
2007-11-01 15:09 ` [PATCH] Document that using -M without other diff options is not a good idea Johannes Schindelin
2007-11-01 15:24 ` Miklos Vajna
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=1193929060-6183-2-git-send-email-vmiklos@frugalware.org \
--to=vmiklos@frugalware.org \
--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).