git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: "Git Mailing List" <git@vger.kernel.org>,
	"Lukas Sandström" <lukass@etek.chalmers.se>
Subject: Re: [PATCH] In Examples, explain option -r and refer to git-rev-list[1]
Date: Mon, 27 Aug 2007 01:33:49 -0700	[thread overview]
Message-ID: <7vbqctl6ky.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vy7fxl7hx.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Mon, 27 Aug 2007 01:14:02 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Lukas Sandström <lukass@etek.chalmers.se> writes:
>
>> Jari Aalto wrote:
>>> Signed-off-by: Jari Aalto <jari.aalto@cante.net>
>>> ---
>>>  Documentation/git-log.txt |    3 ++-
>>>  1 files changed, 2 insertions(+), 1 deletions(-)
>>> 
>>> diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
>>> index 49bb539..aa42f0e 100644
>>> --- a/Documentation/git-log.txt
>>> +++ b/Documentation/git-log.txt
>>> @@ -76,7 +76,8 @@ git log -r --name-status release..test::
>>>  
>>>  	Show the commits that are in the "test" branch but not yet
>>>  	in the "release" branch, along with the list of paths
>>> -	each commit modifies.
>>> +	each commit modifies. Opton -r (see gitlink:git-rev-list[1])
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ spelling mistake (option)
>
> I think it makes more sense to make Porcelain including "git
> log" to always recurse in its diff operations (when diff output
> is asked for), in which case the example should simply lose
> the "-r" option.
>
> But that is a post-1.5.3 change.  That's why I am planning to
> drop this patch for now.

The change would probably look something like this.  Testing is
left as an exercise to the readers ;-).

---

 Documentation/git-log.txt     |    2 +-
 Documentation/user-manual.txt |    2 +-
 builtin-log.c                 |    1 +
 3 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 1e6dbd9..5ec547c 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -96,7 +96,7 @@ git log --since="2 weeks ago" \-- gitk::
 	The "--" is necessary to avoid confusion with the *branch* named
 	'gitk'
 
-git log -r --name-status release..test::
+git log --name-status release..test::
 
 	Show the commits that are in the "test" branch but not yet
 	in the "release" branch, along with the list of paths
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 06ab79f..35298e6 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -921,7 +921,7 @@ file such that it contained the given content either before or after the
 commit.  You can find out with this:
 
 -------------------------------------------------
-$  git log --raw -r --abbrev=40 --pretty=oneline -- filename |
+$  git log --raw --abbrev=40 --pretty=oneline -- filename |
 	grep -B 1 `git hash-object filename`
 -------------------------------------------------
 
diff --git a/builtin-log.c b/builtin-log.c
index 13bae31..d6cf9d5 100644
--- a/builtin-log.c
+++ b/builtin-log.c
@@ -258,6 +258,7 @@ int cmd_log(int argc, const char **argv, const char *prefix)
 	git_config(git_log_config);
 	init_revisions(&rev, prefix);
 	rev.always_show_header = 1;
+	rev.diffopt.recursive = 1;
 	cmd_log_init(argc, argv, prefix, &rev);
 	return cmd_log_walk(&rev);
 }

  reply	other threads:[~2007-08-27  8:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26 15:40 [PATCH] In Examples, explain option -r and refer to git-rev-list[1] Jari Aalto
2007-08-27  8:02 ` Lukas Sandström
2007-08-27  8:14   ` Junio C Hamano
2007-08-27  8:33     ` Junio C Hamano [this message]
2007-08-27  8:44       ` Jeff King
2007-08-27  9:55         ` Junio C Hamano
2007-08-27 10:02           ` Jeff King

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=7vbqctl6ky.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jari.aalto@cante.net \
    --cc=lukass@etek.chalmers.se \
    /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).