From: Christian Couder <chriscool@tuxfamily.org>
To: Junio Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH] Document git-show-ref [-s|--hash] option.
Date: Wed, 20 Sep 2006 06:14:54 +0200 [thread overview]
Message-ID: <20060920061454.8fc28c1f.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20060918123241.GA8238@diku.dk>
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
Documentation/git-show-ref.txt | 18 +++++++++++++++++-
1 files changed, 17 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-show-ref.txt b/Documentation/git-show-ref.txt
index 529ea17..b724d83 100644
--- a/Documentation/git-show-ref.txt
+++ b/Documentation/git-show-ref.txt
@@ -9,7 +9,7 @@ SYNOPSIS
--------
[verse]
'git-show-ref' [-q|--quiet] [--verify] [-h|--head] [-d|--dereference]
- [--tags] [--heads] [--] <pattern>...
+ [-s|--hash] [--tags] [--heads] [--] <pattern>...
DESCRIPTION
-----------
@@ -40,6 +40,12 @@ OPTIONS
Dereference tags into object IDs. They will be shown with "^{}"
appended.
+-s, --hash::
+
+ Only show the SHA1 hash, not the reference name. When also using
+ --dereference the dereferenced tag will still be shown after the SHA1,
+ this maybe a bug.
+
--verify::
Enable stricter reference checking by requiring an exact ref path.
@@ -72,6 +78,16 @@ The output is in the format: '<SHA-1 ID>
...
-----------------------------------------------------------------------------
+When using --hash (and not --dereference) the output format is: '<SHA-1 ID>'
+
+-----------------------------------------------------------------------------
+$ git show-ref --heads --hash
+2e3ba0114a1f52b47df29743d6915d056be13278
+185008ae97960c8d551adcd9e23565194651b5d1
+03adf42c988195b50e1a1935ba5fcbc39b2b029b
+...
+-----------------------------------------------------------------------------
+
EXAMPLE
-------
--
1.4.2.1.g4251-dirty
prev parent reply other threads:[~2006-09-20 4:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 12:32 [PATCH] Add man page for git-show-ref Jonas Fonseca
2006-09-20 4:14 ` Christian Couder [this message]
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=20060920061454.8fc28c1f.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).