From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 2/4] uboot: Update to 2011.06
Date: Fri, 08 Jul 2011 09:09:33 -0700 [thread overview]
Message-ID: <4E172BBD.30709@linux.intel.com> (raw)
In-Reply-To: <A9686B58-013C-4390-B43C-3F06E9EDB02B@dominion.thruhere.net>
On 07/01/2011 12:16 AM, Koen Kooi wrote:
>
> Op 1 jul 2011, om 08:54 heeft Saul Wold het volgende geschreven:
>
>> [YOCTO #1198]
>>
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>> ---
>> ...Drop-config.h-include-in-tools-imximage.h.patch | 0
>> ...ove-LDSCRIPT-processing-to-the-top-level-.patch | 0
>> ...kimage_2011.03.bb => u-boot-mkimage_2011.06.bb} | 12 +++++-------
>> .../uboot/{u-boot_2011.03.bb => u-boot_2011.06.bb} | 10 +++++-----
>
> You do realize that people .bbappending 2011.03 are now left out in the cold, right?
My apologies to Saul as I probably contributed to this by not being
explicit in the bug report. As stated in my earlier mail regarding uboot
policy, we should keep at least two revisions of u-boot around to give
people time to migrate to the newer one (if they can at all).
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-07-08 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 6:54 Updated [PATCH 0/4] SRC_URI Check Updates with Beagleboard updates Saul Wold
2011-07-01 6:54 ` [PATCH 1/4] x-load: Update to 1.5.0 Saul Wold
2011-07-01 6:54 ` [PATCH 2/4] uboot: Update to 2011.06 Saul Wold
2011-07-01 7:16 ` Koen Kooi
2011-07-08 16:09 ` Darren Hart [this message]
2011-07-01 6:54 ` [PATCH 3/4] mpeg2dec: add SRC_URI Checksum Saul Wold
2011-07-01 6:54 ` [PATCH 4/4] libmad: " Saul Wold
2011-07-05 13:17 ` Updated [PATCH 0/4] SRC_URI Check Updates with Beagleboard updates Richard Purdie
2011-07-05 13:35 ` Koen Kooi
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=4E172BBD.30709@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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