From: akuster808 <akuster808@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>,
openembedded-core@lists.openembedded.org
Subject: Re: Hints on submitting to OE-Core
Date: Sat, 18 Mar 2017 01:42:06 -0700 [thread overview]
Message-ID: <bdebc471-dded-69fb-1ae1-d27e1ec751ed@gmail.com> (raw)
In-Reply-To: <3a6a7bd6-a5e5-b139-bc2a-53d3b6b41da5@mlbassoc.com>
On 03/17/2017 06:21 PM, Gary Thomas wrote:
> On 2017-03-18 00:55, Daniel Dickinson wrote:
>> Hi all,
>>
>> I've got a pre-alpha 'distro' and some layers I think that could get to
>> an interesting state. The intent is to work them up to where they are
>> suitable to be submitted as patches to oe-core rather than the
>> current .bbappend and related files.
>>
>> There's rather a lot of reading (which is good in the sense that I like
>> actually have documentation, although that's definitely an area I need
>> to improve on for the layers I've got in the works), and I haven't
>> nearly got through it all yet, but I was hoping for pointers on the
>> most important bits to read for prepping patches submission.
>
> Have you read this?
> http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
To be honest, OE-core does not even comply to the basic standard of a
README. It missing patch submission info like many other layers do nor
does in include the Maintainer.
- armin
>
>>
>> Also, in the layers list I'll be asking about some build issues that I
>> don't see with a manual bitbake, that look like missing preqs on a build
>> server, unless the layer should be requesting installation of host files
>> somewhere.
>
> Some tools required by ${HOSTTOOLS} are missing:
> cpio chrpath gawk diffstat makeinfo
>
next prev parent reply other threads:[~2017-03-18 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 23:55 Hints on submitting to OE-Core Daniel Dickinson
2017-03-18 1:21 ` Gary Thomas
2017-03-18 1:38 ` Daniel Dickinson
2017-03-18 2:17 ` Khem Raj
2017-03-18 2:36 ` Daniel Dickinson
2017-03-18 8:42 ` akuster808 [this message]
2017-03-18 17:17 ` Daniel Dickinson
2017-03-18 19:05 ` Daniel Dickinson
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=bdebc471-dded-69fb-1ae1-d27e1ec751ed@gmail.com \
--to=akuster808@gmail.com \
--cc=gary@mlbassoc.com \
--cc=openembedded-core@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.