From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Rogerio Nunes <ronunes@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: RFC regarding glimagesink
Date: Mon, 29 Jul 2013 08:08:26 -0700 [thread overview]
Message-ID: <51F6856A.6080702@boundarydevices.com> (raw)
In-Reply-To: <CACb8hfF450XQv5mkmMBMVtgXOjd3vQ14dqByLcE=ggo3yx+9dg@mail.gmail.com>
Thanks Rogerio,
On 07/29/2013 07:35 AM, Rogerio Nunes wrote:
> Hi Eric,
>
> I've been usually working without X, so don't know much about glimagesink.
> I have some comments about bitbuck branches bellow.
>
Note that my testing was also without X.
> On Sun, Jul 28, 2013 at 7:44 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi all,
>>
>> <snip>
>>
>> By the way, the attached patch is against branch fsl-0.10
>> in the Bitbucket tree, which appears to match up with the
>> Yocto build, but I notice that Jeremy has a patch applied
>> in the Yocto-0.10.
>>
>> Is 'fsl-0.10' the right baseline to use for future work?
>
> fsl-0.10 - branch with "as is" code from fsl BSPs.
>
> yocto-0.10 - branch with patch(es) from the poky layer
>
> 0.10 - branch to merge fsl-0.10, yocto-0.10, upstream-0.10 and to
> refactor the code to port to master (still ongoing)
>
That's good to know.
Regards,
Eric
next prev parent reply other threads:[~2013-07-29 15:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 23:44 RFC regarding glimagesink Eric Nelson
2013-07-29 14:35 ` Rogerio Nunes
2013-07-29 15:08 ` Eric Nelson [this message]
2013-07-29 19:29 ` Rogerio Nunes
2013-07-29 19:54 ` Eric Nelson
2013-07-29 20:06 ` Otavio Salvador
2013-07-29 20:11 ` Rogerio Nunes
2013-07-29 20:12 ` Eric Nelson
2013-07-29 20:24 ` Rogerio Nunes
2013-07-29 20:28 ` Rogerio Nunes
2013-07-29 20:06 ` Rogerio Nunes
2013-07-30 9:06 ` Thomas Senyk
2013-07-30 9:52 ` Abhijit Potnis
2013-07-30 10:58 ` Thomas Senyk
2013-07-30 14:14 ` Rogerio Nunes
2013-07-30 14:38 ` Thomas Senyk
2013-07-30 17:26 ` Rogerio Nunes
2013-08-01 8:47 ` Abhijit Potnis
2013-08-01 12:50 ` Otavio Salvador
2013-08-01 13:05 ` Rogerio Nunes
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=51F6856A.6080702@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=meta-freescale@yoctoproject.org \
--cc=ronunes@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.