All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>
Subject: [PATCH 02/11] Document git log --full-diff
Date: Sat, 16 Jun 2007 21:03:38 +0200	[thread overview]
Message-ID: <11820206312866-git-send-email-jnareb@gmail.com> (raw)
In-Reply-To: <11820206272990-git-send-email-jnareb@gmail.com>

Based on description of commit 477f2b41310c4b1040a9e7f72720b9c39d82caf9
"git log --full-diff" adding this option.

Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
 Documentation/git-log.txt |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index c072441..7adcdef 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -54,6 +54,13 @@ include::pretty-options.txt[]
 --decorate::
 	Print out the ref names of any commits that are shown.
 
+--full-diff::
+	Without this flag, "git log -p <paths>..." shows commits that
+	touch the specified paths, and diffs about the same specified
+	paths.  With this, the full diff is shown for commits that touch
+	the specified paths; this means that "<paths>..." limits only
+	commits, and doesn't limit diff for those commits.
+
 <paths>...::
 	Show only commits that affect the specified paths.
 
-- 
1.5.2

  parent reply	other threads:[~2007-06-16 18:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 19:03 [PATCH 00/11] Document missing options Jakub Narebski
2007-06-16 19:03 ` [PATCH 01/11] Use tabs for indenting definition list for options in git-log.txt Jakub Narebski
2007-06-16 19:03 ` Jakub Narebski [this message]
2007-06-16 19:03 ` [PATCH 03/11] Document git log --abbrev-commit, as a kind of pretty option Jakub Narebski
2007-06-16 19:03 ` [PATCH 04/11] Document that '--message=<msg>' is long version of '-m <msg>' Jakub Narebski
2007-06-16 19:03 ` [PATCH 05/11] Document that '--no-checkout' is long version of '-n' option of git-clone Jakub Narebski
2007-06-16 19:03 ` [PATCH 06/11] Document git rev-list --timestamp Jakub Narebski
2007-06-16 19:03 ` [PATCH 07/11] Document git rev-list --full-history Jakub Narebski
2007-06-16 19:03 ` [PATCH 08/11] Document git rev-parse --is-inside-git-dir Jakub Narebski
2007-06-16 19:03 ` [PATCH 09/11] Document git read-tree --trivial Jakub Narebski
2007-06-16 19:03 ` [PATCH 10/11] Document git reflog --stale-fix Jakub Narebski
2007-06-16 19:03 ` [PATCH 11/11] Document git commit --untracked-files and --verbose Jakub Narebski
2007-06-16 20:06   ` Junio C Hamano
2007-06-16 22:29     ` Jakub Narebski

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=11820206312866-git-send-email-jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.