Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Thomas Koeller <thomas@koeller.dyndns.org>, linux-mips@linux-mips.org
Subject: Re: git problem
Date: Thu, 29 Nov 2007 15:38:41 +0100	[thread overview]
Message-ID: <474ECEF1.3090206@gmail.com> (raw)
In-Reply-To: <20071129130903.GB14655@linux-mips.org>

Ralf Baechle wrote:
> Back to the original topic - git describe fails even with some of the
> very old commits of the lmo tree which are known to be tagged so there
> is something wrong.

Your issue seems different from Thomas' one. In your case:

	$ git cat-file -t refs/tags/linux-1.3.0
	commit

So the tag you mentioned is a _lightweight_ tag. These are not
considered by git-describe by default.

To make git-describe work, just do:

	$ git describe --tags $(cat .git/refs/tags/linux-1.3.0)
	linux-1.3.0

		Franck

  reply	other threads:[~2007-11-29 14:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 18:50 git problem Thomas Koeller
2007-11-28 20:19 ` Ralf Baechle
2007-11-29 11:32 ` Franck Bui-Huu
2007-11-29 13:09   ` Ralf Baechle
2007-11-29 14:38     ` Franck Bui-Huu [this message]
2007-11-29 15:06       ` Ralf Baechle
2007-11-29 22:47   ` Thomas Koeller

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=474ECEF1.3090206@gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=thomas@koeller.dyndns.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