From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Merging RPs branch, help needed for dealing with possible fall-out
Date: Thu, 29 Apr 2010 20:20:55 +0200 [thread overview]
Message-ID: <hrcim7$8ge$1@dough.gmane.org> (raw)
In-Reply-To: <1272552574.3865.814.camel@trini-m4400>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 29-04-10 16:49, Tom Rini wrote:
> On Thu, 2010-04-29 at 12:18 +0200, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> I've been talking to RP and we both like to merge his branch as soon as
>> the last problem (the cross lamanger) has been addressed. RP estimates
>> that will happen early next week.
>> But after it has been merged there might be some fallout, which we would
>> like to have some help with. If you don't want to help out and and don't
>> want the possible breakage: don't git pull for the time being.
>
> Related, do we have people signing up for building ___ targets? I'll
> assume angstrom + beagleboard + beagleboard-demo will be covered :)
I'm going to do angstrom + beagle/hawkboard +
console/beagleboard-demo/angstrom-gnome-image
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL2c4HMkyGM64RGpERAuYlAKCejfFnK3vrXTMGjI3iVMe4CFKNNACgs27T
3hMCl0G2qFrlr6Xs2e6YaeQ=
=COBt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-29 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 10:18 Merging RPs branch, help needed for dealing with possible fall-out Koen Kooi
2010-04-29 14:49 ` Tom Rini
2010-04-29 18:20 ` Koen Kooi [this message]
2010-04-30 17:41 ` Denys Dmytriyenko
2010-04-30 19:20 ` Khem Raj
2010-04-30 14:04 ` Stefan Schmidt
2010-04-30 14:10 ` Martin Jansa
2010-04-30 14:38 ` Michael Lippautz
2010-05-01 0:10 ` Tom Rini
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='hrcim7$8ge$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-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