Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] rt-tests: use an explicit commit ID
Date: Fri, 12 Aug 2011 17:51:36 +0100	[thread overview]
Message-ID: <1313167896.14274.515.camel@rex> (raw)
In-Reply-To: <ffa3108cb68e977a91414eeff183275c92800461.1313167004.git.dvhart@linux.intel.com>

On Fri, 2011-08-12 at 09:42 -0700, Darren Hart wrote:
> Using a tag, like v0.73, forces network access to resolve a
> commit ID. Use the corresponding commit ID in the recipe.
> 
> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
> ---
>  meta/recipes-rt/rt-tests/rt-tests_0.73.bb |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/meta/recipes-rt/rt-tests/rt-tests_0.73.bb b/meta/recipes-rt/rt-tests/rt-tests_0.73.bb
> index 6334bcd..a2cf6be 100644
> --- a/meta/recipes-rt/rt-tests/rt-tests_0.73.bb
> +++ b/meta/recipes-rt/rt-tests/rt-tests_0.73.bb
> @@ -6,7 +6,8 @@ LICENSE = "GPLv2 & GPLv2+"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
>                      file://src/cyclictest/cyclictest.c;beginline=7;endline=9;md5=ce162fe491d19d2ec67dff6dbc938d50 \
>                      file://src/pi_tests/pi_stress.c;beginline=6;endline=19;md5=bd426a634a43ec612e9fbf125dfcc949"
> -SRCREV = v0.73
> +# Version v0.73
> +SRCREV = "81da016fb0f6ab0511fbec81fc8ba1a50398a20d"
>  PV = "git${SRCPV}"
>  PR = "r0"

Merged to master, thanks.

Richard





      reply	other threads:[~2011-08-12 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 16:42 [PATCH 0/1] rt-tests: use an explicit commit ID Darren Hart
2011-08-12 16:42 ` [PATCH 1/1] " Darren Hart
2011-08-12 16:51   ` Richard Purdie [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=1313167896.14274.515.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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