Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Explaining the patches that will be send ...
Date: Sun, 24 Oct 2010 15:10:22 +0200	[thread overview]
Message-ID: <ia1b7v$p2e$2@dough.gmane.org> (raw)
In-Reply-To: <20101024062941.GE3494@jama>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24-10-10 08:29, Martin Jansa wrote:
> On Fri, Oct 22, 2010 at 10:13:40PM -0200, Fabiano Fidêncio wrote:
>> Howdy!
>>
>> Guys, I'll send a lot of patches made by Eduardo Lima (Etrunko) and I
>> via git send-mail.
>>
>> This patches are creating/fixing svn build from some
>> {EFL,LMS,WebKit-EFL} packages and are keeping in three differents
>> branchs of my git tree. All of this are rebased with the latest HEAD.
>>
>> Please, apply if correct :-)
> 
> Today I'll apply those where was no reply from me or koen, for the rest
> please send updated patches with v2 prefix.

I think I have a way to make the gles situation less worse for TI
targets[1], I need to work on that patch a bit. I'll be too busy next
week to get it done, though.

regards,

Koen

[1] Those are the only armv7a targets with recipes for gles drivers in
the tree.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMxDA+MkyGM64RGpERAqOkAJ44aV8nmSr3/GrFBkRctYX7EkEpowCfW97i
aJiScZbUlCx+QuOhJNTvrFE=
=jIKn
-----END PGP SIGNATURE-----




      parent reply	other threads:[~2010-10-24 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=fqKeS6eu1H5mS-C7rQeJPndf8Xchpghaxjh_d@mail.gmail.com>
2010-10-23  0:13 ` Explaining the patches that will be send Fabiano Fidêncio
2010-10-24  6:29   ` Martin Jansa
2010-10-24  6:32     ` Fabiano Fidêncio
2010-10-24  6:40       ` Martin Jansa
2010-10-24 13:10     ` Koen Kooi [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='ia1b7v$p2e$2@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