From: Baruch Siach <baruch@tkos.co.il>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Barebox 'git describe' strangeness
Date: Thu, 1 Jul 2010 10:55:51 +0300 [thread overview]
Message-ID: <20100701075551.GH16981@jasper.tkos.co.il> (raw)
In-Reply-To: <20100701074739.GB12115@pengutronix.de>
Hi Sascha,
On Thu, Jul 01, 2010 at 09:47:39AM +0200, Sascha Hauer wrote:
> On Thu, Jul 01, 2010 at 09:28:22AM +0200, Eric Bénard wrote:
> > Le 01/07/2010 09:13, Baruch Siach a écrit :
> >> Hi barebox list,
> >>
> >> For some reason 'git describe' shows me:
> >>
> >> v2009.12.0-178-gdc882c3
> >>
> >> I.e. git doesn't find the more recent v2010.06.0 tag. What is worse is that
> >> the top-level Makefile takes the '-178-gdc882c3' part and attaches it to
> >> '2010.06.0', making the output of the 'version' command:
> >>
> >> barebox 2010.06.0-00178-gcc827a1 (Jul 1 2010 - 09:02:45)
> >>
> >> which is plain wrong.
> >>
> >> Can anyone here explain what's going on?
> >>
> > same thing here (the man says "By default (without --all or --tags) git
> > describe only shows annotated tags." so maybe the tags after 2009.12.0
> > are not annotated ?)
>
> No, they are not. Sorry, I'm still learning git...
>
> I will fix this from the next release on.
I've posted a patch adding --tags to 'git describe'. This should fix the
problem for older tags.
Thanks Eric.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2010-07-01 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 7:13 Baruch Siach
2010-07-01 7:28 ` Eric Bénard
2010-07-01 7:47 ` Sascha Hauer
2010-07-01 7:50 ` Eric Bénard
2010-07-01 7:55 ` Baruch Siach [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=20100701075551.GH16981@jasper.tkos.co.il \
--to=baruch@tkos.co.il \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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