git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Burton <markb@ordern.com>
To: git@vger.kernel.org
Subject: git describe --tags --long barfs on new tags?
Date: Wed, 2 Jul 2008 15:45:06 +0100	[thread overview]
Message-ID: <20080702154506.7b83bae8@crow> (raw)


Howdy folks,

Discovered this today:

~/git[master]$ git tag mb
~/git[master]$ git describe 
v1.5.6.1-156-ge903b40
~/git[master]$ git describe --tags
mb
~/git[master]$ git describe --tags --long
Segmentation fault (core dumped)

Hope this is useful info.

BTW - just started using git and I am very impressed with it - took me a while to get my head around the "index" but now I wonder what the problem was.

Cheers,

Mark

             reply	other threads:[~2008-07-02 14:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02 14:45 Mark Burton [this message]
2008-07-02 19:56 ` git describe --tags --long barfs on new tags? Mikael Magnusson
2008-07-03  2:32   ` [PATCH] Fix describe --tags --long so it does not segfault Shawn O. Pearce
2008-07-03  4:23     ` Junio C Hamano
2008-07-03  2:49   ` git describe --tags --long barfs on new tags? Abhijit Menon-Sen

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=20080702154506.7b83bae8@crow \
    --to=markb@ordern.com \
    --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).