From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Merging RPs branch, help needed for dealing with possible fall-out
Date: Fri, 30 Apr 2010 16:10:44 +0200 [thread overview]
Message-ID: <20100430141044.GC3376@jama> (raw)
In-Reply-To: <20100430140422.GA3403@excalibur.local>
On Fri, Apr 30, 2010 at 04:04:22PM +0200, Stefan Schmidt wrote:
> Hello.
>
> On Thu, 2010-04-29 at 07:49, Tom Rini wrote:
> > On Thu, 2010-04-29 at 12:18 +0200, Koen Kooi wrote:
> > >
> > > 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 can take care of imote2, the ezx devices and sgh-i900. All armv5.
>
> I bet the SHR guys are taking care about om-gta02 and om-gta01. Which would be
> armv4.
Sure I can cover
SHR + om-gta0* + shr-images
and try
Angstrom + spitz + x11-gpe-image
Regards,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next prev parent reply other threads:[~2010-04-30 14:14 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
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 [this message]
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=20100430141044.GC3376@jama \
--to=martin.jansa@gmail.com \
--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