From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Scott Rifenbark <srifenbark@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: 2.6 planning proposals and meeting
Date: Thu, 3 May 2018 07:29:19 +0000 [thread overview]
Message-ID: <5e09a0d81b0a48a1bebdc3e8ed542f52@XBOX02.axis.com> (raw)
In-Reply-To: <CAFNP8Ov2waP_aG81Y9_AJRNbm4FicjhkC7Yy-M5OU=SXLmJarg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]
From: openembedded-core-bounces@lists.openembedded.org [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of Scott Rifenbark
Sent: den 1 maj 2018 16:56
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] 2.6 planning proposals and meeting
On Tue, May 1, 2018 at 7:46 AM, Richard Purdie <richard.purdie@linuxfoundation.org<mailto:richard.purdie@linuxfoundation.org>> wrote:
Hi,
On Fri, 2018-04-20 at 08:02 -0400, Daniel F. Dickinson wrote:
> I'm relatively new to OE; I've written a couple of pre-alpha layers
> to try some idea, and worked on meta-openembedded, but I've not had a
> chance to go in depth on the Yocto documentation, and at the some
> there see to be things (based on the lists) that are out of date, or
> new things that aren't even mentioned, which makes getting up speed
> somewhat difficult.
Writing down where you think there are issues would be a help so that
we can see if there is some way we can improve that.
Yes - please indicate any areas in the documentation you believe need updated, changed, or added. I have been trying to bring things up-to-date in several manuals during the 2.5 process. So, identifying areas in the 2.5 manual set would be very helpful. To be sure you are viewing 2.5 manuals use the following form for the URL:
yoctoproject.org/docs/2.5/<http://yoctoproject.org/docs/2.5/><manual_folder>/<manual_folder>.html
where <manual_folder> is
brief-yoctoprojectqs
bsp-guide
overview-manual
dev-manual
sdk-manual
profile-manual
kernel-dev
ref-manual
toaster-manual
bitbake-user-guide
Thanks
Scott
Is there any special process to get manual updates accepted? I am asking because I sent an update for the BUILDHISTORY_FEATURES variable to the Yocto mailing list (https://lists.yoctoproject.org/pipermail/yocto/2018-January/039787.html) at the end of January (last pinged a month ago) and it still has not made it into the manual AFAICT and it has not received any feedback.
//Peter
[-- Attachment #2: Type: text/html, Size: 7068 bytes --]
next prev parent reply other threads:[~2018-05-03 7:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 16:17 2.6 planning proposals and meeting Richard Purdie
2018-04-19 19:02 ` [Openembedded-architecture] " akuster808
2018-04-20 12:02 ` Daniel F. Dickinson
2018-05-01 14:46 ` Richard Purdie
2018-05-01 14:55 ` Scott Rifenbark
2018-05-03 7:29 ` Peter Kjellerstedt [this message]
2018-05-03 12:42 ` Scott Rifenbark
2018-05-03 13:58 ` Scott Rifenbark
2018-05-06 0:42 ` Daniel F. 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=5e09a0d81b0a48a1bebdc3e8ed542f52@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=srifenbark@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox