Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: Olof Johansson <olof.johansson@axis.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: ^{} what is it good for? (bitbake problem)
Date: Wed, 04 Jun 2014 16:21:00 +0200	[thread overview]
Message-ID: <538F2B4C.10704@dresearch-fe.de> (raw)
In-Reply-To: <20140604082943.GA11527@axis.com>

On 04.06.2014 10:29, Olof Johansson wrote:
> On 14-06-04 10:06 +0200, Steffen Sledz wrote:
>> So what is this ^{} which comes from lib/bb/fetch2/git.py good for?
>> Or is this a remnant from a typo?
> 
> From git-rev-parse(1):
> 
>   <rev>^{}, e.g. v0.99.8^{}
>       A suffix ^ followed by an empty brace pair means the object could be a
>       tag, and dereference the tag recursively until a non-tag object is
>       found.
> 
> Without this change, (some?) tag references would end up not
> being considered to be on the requested branch by bitbake (by
> default, master), as the tag objects themselves are not. The tags
> therefore have to be resolved to a reference to a commit.
> 
> Given the description in git-rev-parse(1), it surprises me that
> it doesn't work for some cases. I think it has to do with the tag
> being annotated or not.

You were right. The method works with annotated tags only. I've changed the related tags.

Thx,
Steffen

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058


      reply	other threads:[~2014-06-04 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  8:06 ^{} what is it good for? (bitbake problem) Steffen Sledz
2014-06-04  8:29 ` Olof Johansson
2014-06-04 14:21   ` Steffen Sledz [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=538F2B4C.10704@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=olof.johansson@axis.com \
    --cc=openembedded-core@lists.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