From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: How to verify patches for oe-dev master?
Date: Mon, 12 Sep 2011 16:46:13 +0200 [thread overview]
Message-ID: <4E6E1B35.7040709@gmail.com> (raw)
In-Reply-To: <4E6E14EC.1000301@dresearch-fe.de>
Steffen Sledz ha scritto, Il 12/09/2011 16:19:
> On 09.09.2011 12:23, Steffen Sledz wrote:
>> At the moment we're using the 2011.03-maintenance branch with angstrom-2008.1, and we have a problem verifying patches.
>>
>> Assuming we've found a fix to a bug in 2011.03-maintenance. In my opinion the fix should go to oe-dev master first and find it's way to 2011.03-maintenance by a pull request.
>>
>> The problem is that oe-master does not support angstrom-2008.1 any more, so it's hard to check if the patch compiles/runs well under oe-master.
>
> Let me reword the question.
>
> Which "general purpose" distros are supported by oe-dev master at the moment and can be used to check if a patch applies, compiles, and runs?
>
Hi Steffen,
KaeilOS distro is working in oe-dev master at the moment, but I can't
guarantee that all recipes will work properly with it.
http://www.kaeilos.com/
Feel free to test it if you want.
Tell me more about your system and the issue you are facing to.
Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
--
Marco Cavallini | KOAN sas | Bergamo - Italia
embedded and real-time software engineering
Atmel third party certified consultant
Phone:+39-035-255.235 - Fax:+39-178-22.39.748
http://www.KoanSoftware.com
http://www.KaeilOS.com
next prev parent reply other threads:[~2011-09-12 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 10:23 How to verify patches for oe-dev master? Steffen Sledz
2011-09-12 14:19 ` Steffen Sledz
2011-09-12 14:46 ` Marco Cavallini [this message]
2011-09-12 14:52 ` Steffen Sledz
2011-09-12 15:09 ` Marco Cavallini
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=4E6E1B35.7040709@gmail.com \
--to=koansoftware@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 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.