From: Tomas Carnecky <tom@dbservice.com>
To: Martin Pirker <Martin.Pirker@iaik.tugraz.at>
Cc: git@vger.kernel.org
Subject: Re: git-describe hash length
Date: Thu, 22 Jan 2009 13:34:06 +0100 [thread overview]
Message-ID: <497867BE.8070509@dbservice.com> (raw)
In-Reply-To: <497857CE.3060101@iaik.tugraz.at>
On 01/22/2009 12:26 PM, Martin Pirker wrote:
> Hi!
>
>
> john@doe:/workspace$ git version
> git version 1.6.1
> john@doe:/workspace$ git describe
> fatal: cannot describe '7aee61cc635a923e70b74091486742481ee0928b'
> john@doe:/workspace$ git describe --always
> 7aee61c
> john@doe:/workspace$ git describe --always --abbrev=8
> 7aee61cc
>
>
> man git-describe:
>
> --abbrev=<n>
> Instead of using the default 8 hexadecimal digits as the
> abbreviated object name, use<n> digits.
>
>
>
> There is one character missing from default or what am I missing?
The man page is wrong:
cache.h:#define DEFAULT_ABBREV 7
builtin-describe.c:static int abbrev = DEFAULT_ABBREV;
tom
next prev parent reply other threads:[~2009-01-22 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 11:26 git-describe hash length Martin Pirker
2009-01-22 12:34 ` Tomas Carnecky [this message]
2009-01-22 18:26 ` [PATCH] Fix Documentation for git-describe Boyd Stephen Smith Jr.
2009-01-23 9:36 ` Junio C Hamano
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=497867BE.8070509@dbservice.com \
--to=tom@dbservice.com \
--cc=Martin.Pirker@iaik.tugraz.at \
--cc=git@vger.kernel.org \
/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).