From: Otavio Salvador <otavio@debian.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: [RFH] Support for automatic package versining using git describe
Date: Fri, 13 Feb 2009 08:46:15 -0200 [thread overview]
Message-ID: <87d4dmiphk.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <gn3cpm$tif$1@ger.gmane.org> (Koen Kooi's message of "Fri, 13 Feb 2009 09:59:33 +0100")
Koen Kooi <k.kooi@student.utwente.nl> writes:
> On 13-02-09 03:32, Otavio Salvador wrote:
>> Hello,
>>
>> One of nice features we've been using is the git-describe to get
>> versions based on tags; many projects are using it to name the
>> development releases and it does give a better view of how diverged it
>> from last released version.
>>
>> So we're looking for a way to use it to generate the PV based on
>> that. The current git fetcher already has the required support to get
>> tags, so we can use it as SRCREV, but not yet to use git-describe.
>
> Do you have any examples of the output?
Sure:
otavio@neumann:~/hacking/ossystems/toscoterm$ git describe
0.1-1-gd834119
Basically this can be read as:
- last version was 0.1
- since that we've done 1 commit
- the sha1sum of it is d834119 (g is always included before it)
Cheers,
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
next prev parent reply other threads:[~2009-02-13 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 2:32 [RFH] Support for automatic package versining using git describe Otavio Salvador
2009-02-13 8:59 ` Koen Kooi
2009-02-13 10:46 ` Otavio Salvador [this message]
[not found] <87iqmp5f58.fsf@neumann.lab.ossystems.com.br>
2009-03-04 18:34 ` Mario Domenech Goulart
2009-03-05 13:43 ` Otavio Salvador
2009-03-05 21:31 ` Mario Domenech Goulart
2009-03-05 21:37 ` Koen Kooi
2009-03-06 0:50 ` Mike (mwester)
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=87d4dmiphk.fsf@neumann.lab.ossystems.com.br \
--to=otavio@debian.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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