git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 1/2] git-rev-list.txt: Correct description for multiple arguments
Date: Wed,  5 Aug 2009 09:58:36 +0200	[thread overview]
Message-ID: <1249459117-3853-1-git-send-email-git@drmicha.warpmail.net> (raw)

"git rev-list A B" really lists those commits which are included in A or
B, i.e. it lists those in A and those in B. Say so, because saying
"which are included in A and B" would mean those who are in both A and
B.

Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
Patch against master.

The current description is simply wrong, which is why I strongly suggest this fix.
The upcoming suggests an extra paragraph for clarifying the use of multiple
revision arguments.

 Documentation/git-rev-list.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt
index a765cfa..847cc7d 100644
--- a/Documentation/git-rev-list.txt
+++ b/Documentation/git-rev-list.txt
@@ -63,7 +63,7 @@ command:
 	$ git rev-list foo bar ^baz
 -----------------------------------------------------------------------
 
-means "list all the commits which are included in 'foo' and 'bar', but
+means "list all the commits which are included in 'foo' or 'bar', but
 not in 'baz'".
 
 A special notation "'<commit1>'..'<commit2>'" can be used as a
-- 
1.6.4.70.g9c084

             reply	other threads:[~2009-08-05  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  7:58 Michael J Gruber [this message]
2009-08-05  7:58 ` [PATCH 2/2] git-rev-list.txt: Clarify the use of multiple revision arguments Michael J Gruber
2009-08-05 16:42   ` Junio C Hamano
2009-08-06  8:48     ` Michael J Gruber

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=1249459117-3853-1-git-send-email-git@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --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).