From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Subject: [PATCH 1/4] rev-parse: deprecate use as an option sifter
Date: Thu, 13 May 2010 16:24:35 +0200 [thread overview]
Message-ID: <725860e3bfc692c7241695ef5f554ff73f277b15.1273760226.git.git@drmicha.warpmail.net> (raw)
In-Reply-To: <20100505033536.GB8779@coredump.intra.peff.net>
In-Reply-To: <cover.1273760226.git.git@drmicha.warpmail.net>
This command used to be used to distinguish between parameters meant
for rev-list and others, but this is deprectated now, and one should not
rely on rev-parse keeping up to date with rev-list. State this in the
man page and reword the title according to the primary use (converting
symbolic names to SHA1's).
Reference: <http://permalink.gmane.org/gmane.comp.version-control.git/146118>
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
Documentation/git-rev-parse.txt | 14 ++++++++++----
1 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index 8db600f..99d2a79 100644
--- a/Documentation/git-rev-parse.txt
+++ b/Documentation/git-rev-parse.txt
@@ -3,7 +3,7 @@ git-rev-parse(1)
NAME
----
-git-rev-parse - Pick out and massage parameters
+git-rev-parse - Parse symbolic names into object names
SYNOPSIS
@@ -13,12 +13,18 @@ SYNOPSIS
DESCRIPTION
-----------
-Many git porcelainish commands take mixture of flags
+The primary use of 'git rev-parse' is to turn symbolic object names into
+40-letter object names ("SHA-1").
+
+Also, many git porcelainish commands take a mixture of flags
(i.e. parameters that begin with a dash '-') and parameters
meant for the underlying 'git rev-list' command they use internally
and flags and parameters for the other commands they use
-downstream of 'git rev-list'. This command is used to
-distinguish between them.
+downstream of 'git rev-list'. This command used to be used to
+distinguish between them, but this is deprectated now, and you should
+not expect 'git rev-parse' to keep up to date with newer parameters for
+'git rev-list'. You can use linkgit:git-rev-list[1] directly or
+linkgit:git-for-each-ref[1] for scripting.
OPTIONS
--
1.7.1.240.geeaa4d
next prev parent reply other threads:[~2010-05-13 14:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 18:36 [RFD PATCH] revlist/rev-parse: Introduce --heads and --locals revision specifiers Michael J Gruber
2010-05-01 19:42 ` Jakub Narebski
2010-05-01 19:47 ` Michael J Gruber
2010-05-01 19:51 ` Jakub Narebski
2010-05-02 5:00 ` Jeff King
2010-05-02 13:43 ` Michael J Gruber
2010-05-05 3:35 ` Jeff King
2010-05-13 14:24 ` [PATCH 0/4] All is too much Michael J Gruber
2010-05-13 14:24 ` Michael J Gruber [this message]
2010-05-14 15:41 ` [PATCH 1/4] rev-parse: deprecate use as an option sifter Jakub Narebski
2010-05-14 18:52 ` Michael J Gruber
2010-05-14 19:01 ` Jakub Narebski
2010-05-14 19:22 ` Michael J Gruber
2010-05-17 14:26 ` Thomas Rast
2010-05-13 14:24 ` [PATCH 2/4] t6018: add tests for rev-list's --branches and --tags Michael J Gruber
2010-05-13 14:24 ` [PATCH 3/4] t6018: make sure all tested symbolic names are different revs Michael J Gruber
2010-05-13 14:24 ` [PATCH 4/4] revlist: Introduce --lrbranches and --locals revision specifiers Michael J Gruber
2010-05-14 6:06 ` [PATCH 0/4] All is too much Jeff King
2010-05-14 16:08 ` Michael J Gruber
2010-05-14 16:14 ` Git methodology question Akhbari, Farshad
2010-05-14 21:44 ` Chris Packham
2010-05-14 21:54 ` Avery Pennarun
2010-05-14 18:26 ` [PATCH v2 0/4] All is too much Michael J Gruber
2010-05-14 18:26 ` [PATCH v2 1/4] rev-parse: deprecate use as an option sifter Michael J Gruber
2010-05-14 18:26 ` [PATCH v2 2/4] t6018: add tests for rev-list's --branches and --tags Michael J Gruber
2010-05-14 18:26 ` [PATCH v2 3/4] t6018: make sure all tested symbolic names are different revs Michael J Gruber
2010-05-14 18:26 ` [PATCH v2 4/4] revlist: Introduce --lrbranches and --locals revision specifiers 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=725860e3bfc692c7241695ef5f554ff73f277b15.1273760226.git.git@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).