Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Saul Wold <saul.wold@intel.com>
Cc: Robert Berger <pokylinux@reliableembeddedsystems.com>,
	Yi Zhao <yi.zhao@windriver.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] u-boot: update SRCREV to 2011.03
Date: Thu, 19 May 2011 18:55:08 -0700	[thread overview]
Message-ID: <4DD5C9FC.9000101@linux.intel.com> (raw)
In-Reply-To: <4DD5C275.9000101@intel.com>



On 05/19/2011 06:23 PM, Saul Wold wrote:
> On 05/18/2011 03:05 PM, Darren Hart wrote:
>> From: Darren Hart<dvhart@linux.intel.com>
>>
>> Pull URL: git://git.pokylinux.org/poky-contrib.git
>>    Branch: dvhart/beagle
>>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/beagle
>>
>> Thanks,
>>      Darren Hart<dvhart@linux.intel.com>
>> ---
>>
>>
>> Darren Hart (1):
>>    u-boot: update SRCREV to 2011.03
>>
>>   meta/recipes-bsp/uboot/u-boot_git.bb |    8 ++++----
>>   1 files changed, 4 insertions(+), 4 deletions(-)
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
> Pulled, but it had a problem with MD5SUM for the readme!
> 
> I did not catch that as I should have, I have an updated recipe and will 
> send it up in tonight's pull request.

This built for me as is, I'm curious what would have triggered a
problem. In particular, if my testing process is broken, I want to fix it.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



  reply	other threads:[~2011-05-20  1:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 22:05 [PATCH 0/1] u-boot: update SRCREV to 2011.03 Darren Hart
2011-05-18 22:05 ` [PATCH 1/1] " Darren Hart
2011-05-20  1:23 ` [PATCH 0/1] " Saul Wold
2011-05-20  1:55   ` Darren Hart [this message]
2011-05-20  3:07     ` Saul Wold

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=4DD5C9FC.9000101@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pokylinux@reliableembeddedsystems.com \
    --cc=saul.wold@intel.com \
    --cc=yi.zhao@windriver.com \
    /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