From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/1] Fixes for the Git fetcher
Date: Mon, 23 May 2016 13:35:48 +0200 [thread overview]
Message-ID: <cover.1464003299.git.pkj@axis.com> (raw)
This fixes a problem with the Git fetcher where it could assign the
wrong SHA-1 to a Git reference. The problem was that the matching done
in _latest_revision() wasn't exact, which means that, e.g., SRCREV =
"R${PV}" where PV = "1.0" would match a tag called R1.0.0, rather than
fail as it should since the tag R1.0 does not exist.
//Peter
The following changes since commit c7e614c438706fb3ed7520b4990ebb3973366942:
useradd: Fix infinite build loop (2016-05-23 10:33:45 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib pkj/exact_git_refs
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/exact_git_refs
Peter Kjellerstedt (1):
fetch2/git.py: References must match exactly
bitbake/lib/bb/fetch2/git.py | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--
2.1.0
next reply other threads:[~2016-05-23 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 11:35 Peter Kjellerstedt [this message]
2016-05-23 11:35 ` [PATCH 1/1] fetch2/git.py: References must match exactly Peter Kjellerstedt
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=cover.1464003299.git.pkj@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=bitbake-devel@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