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

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.

  reply	other threads:[~2007-08-27  8:14 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 [this message]
2007-08-27  8:33     ` Junio C Hamano
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=7vy7fxl7hx.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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).