From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 87B4BE009DF; Fri, 4 May 2018 09:53:54 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (srifenbark[at]gmail.com) * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [209.85.218.53 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com [209.85.218.53]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4679AE005A9 for ; Fri, 4 May 2018 09:53:52 -0700 (PDT) Received: by mail-oi0-f53.google.com with SMTP id y15-v6so19729513oia.13 for ; Fri, 04 May 2018 09:53:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pQPdEpeRszXidLJH2bl7AEmf/+ZmlCxK2lcmQJBYlfQ=; b=QpluP+xc4MIdhuf8aMwti+mmu+1QaOdm1REHeUfmPJ49DIftu/pXhNk5Ip9Dsl4Qk7 Sx8AkSYbwtOIXo33XFpA3QSMLhFM/3vLebuCeavRfYxsGqfS7OmHJyUqMXlCfLGpGrSf XtHnNHaCHNDO0L26kezuT/0tJy+87NrwgftX8CNRV0vtXpLmqsZGq0vKD6WYrUwu43vK y5LnF+z3rjXxmCFUDWryO7Rc8jlA65dclswPlb3LNINA0qNfYb1iobSiUhW/mrTy/pL4 SHbpmB1xPPiFbHr4nvyefmDasXxP/NzP5H9gydyIO8h+6OyL30LyqQUgtI1Abautua/J ZyRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pQPdEpeRszXidLJH2bl7AEmf/+ZmlCxK2lcmQJBYlfQ=; b=tleWwR/m6zApAwrQraee/VBEAbRf7abISyGON+reqOpJwBZJzZWW8RNTUIJKwGnr/V /iwxWqQJeFE5FjqIfvWI5Bbbp/XB56mp7WEDvjSIJqFNM9S6q1uCt5czh3rX7hpRExmT CBhHLFJMvnHtuTbXuFc1KRhtWP7NBjLSQ2oXiJvtwz/QYxqaiNMtOOd7Xt93kRG3FGhu BnuCyi7FsljATXWMyeJzzyAO5I/8LexW5FsbqjIZP/f4FfhZVkL/FXMrgeYZ690KDQne mLccuASdTk3Q/NBTVY1LUz3mavpOGqt0vXo4GprcriMxPZ2kt/kaXYB9/OoJeopP8myC iJGw== X-Gm-Message-State: ALQs6tAZKnMRQQAw+EtFK4Nob/LSSbm2lv01GOm/wRoaETsjdjq8+TyE 2wOgB/HYOKLRhO3s4+ZZBiZV5DwUJVB2qLW50AQ= X-Google-Smtp-Source: AB8JxZqnvLPj1WZAYnqvYZfjxHOv9Dh9HViXRPKRQ1a/3fJ54BaVh8b/plVIkWiyn5KGpJmiNz4/YA0n47ZpfssmzAI= X-Received: by 2002:aca:e2cf:: with SMTP id z198-v6mr11919240oig.187.1525452832474; Fri, 04 May 2018 09:53:52 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:7009:0:0:0:0:0 with HTTP; Fri, 4 May 2018 09:53:51 -0700 (PDT) In-Reply-To: <1de735f1d8b44901b57403f49bca0611@XBOX02.axis.com> References: <1524154643.18865.113.camel@linuxfoundation.org> <39f087be-1129-6131-d5d1-5714f127667b@thecshore.com> <1525186011.25196.117.camel@linuxfoundation.org> <5e09a0d81b0a48a1bebdc3e8ed542f52@XBOX02.axis.com> <1de735f1d8b44901b57403f49bca0611@XBOX02.axis.com> From: Scott Rifenbark Date: Fri, 4 May 2018 09:53:51 -0700 Message-ID: To: Peter Kjellerstedt Cc: Yocto discussion list Subject: Re: [OE-core] 2.6 planning proposals and meeting X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2018 16:53:54 -0000 Content-Type: multipart/alternative; boundary="000000000000338e03056b642afa" --000000000000338e03056b642afa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry man... I just stuck the new one in there. Alphabetical would be best. I will fix that. Thanks, Scott On Fri, May 4, 2018 at 9:26 AM, Peter Kjellerstedt < peter.kjellerstedt@axis.com> wrote: > Not sure why you reordered the descriptions of the features from > image,package,sdk,task to image,task,package,sdk (I added =E2=80=9Ctask= =E2=80=9D at the end > since that kept them sorted alphabetically), but apart from that it looks > fine to me. > > > > //Peter > > > > *From:* Scott Rifenbark [mailto:srifenbark@gmail.com] > *Sent:* den 3 maj 2018 15:58 > *To:* Peter Kjellerstedt > *Cc:* Richard Purdie ; > openembedded-core ; Yocto > discussion list > > *Subject:* Re: [OE-core] 2.6 planning proposals and meeting > > > > Hi Peter, > > Thanks for the patch. I have applied it to the 2.5 version of the Yocto > Project Reference Manual (see https://yoctoproject.org/docs/ > 2.5/ref-manual/ref-manual.html#var-BUILDHISTORY_FEATURES). You can also > see https://yoctoproject.org/docs/2.5/ref-manual/ref-manual. > html#var-BUILDHISTORY_FEATURES for the commit in the yocto-docs > repository. > > Please look it over as I did a bit of modification for manual purposes. > > Regards, > > Scott > > > > On Thu, May 3, 2018 at 12:29 AM, Peter Kjellerstedt < > peter.kjellerstedt@axis.com> wrote: > > > > > > *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 > *Cc:* openembedded-core > *Subject:* Re: [OE-core] 2.6 planning proposals and meeting > > > > On Tue, May 1, 2018 at 7:46 AM, 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-dat= e > 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//.html > > where 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 a= ny > feedback. > > //Peter > > > > > --000000000000338e03056b642afa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry man... I just stuck the new one in there.= =C2=A0 Alphabetical would be best.=C2=A0 I will fix that.

Tha= nks,
Scott

On Fri, May 4, 2018 at 9:26 AM, Peter Kjellerstedt <peter.kjellerstedt@axis.com> wrote:

Not sur= e why you reordered the descriptions of the features from image,package,sdk= ,task to image,task,package,sdk (I added =E2=80=9Ctask=E2=80=9D at the end = since that kept them sorted alphabetically), but apart from that it looks fine to me.

= =C2=A0

//Peter=

= =C2=A0

From: Scott Rifenbark [mailto:srifenbark@gmail.com]
Sent: den 3 maj 2018 15:58
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>;= openembedded-core <openembedded-core@lists.openembedded.org= >; Yocto discussion list <yocto@yoctoproject.org>


Subject: Re: [OE-core] 2.6 planning proposals and meeting<= /u>

=C2=A0

Hi Peter, <= /u>

Thanks for the patch.= =C2=A0 I have applied it to the 2.5 version of the Yocto Project Reference = Manual (see https://yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#var-= BUILDHISTORY_FEATURES).=C2=A0 You can also see https://yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#var-= BUILDHISTORY_FEATURES for the commit in the yocto-docs repository.

Please look it over a= s I did a bit of modification for manual purposes.

Regards,

Scott

=C2=A0

On Thu, May 3, 2018 at 12:29 AM, Peter Kjellerstedt = <peter.= kjellerstedt@axis.com> wrote:

=C2=A0<= /span>

=C2=A0<= /span>

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><= br> Cc: openembedded-core <openembedded-core@lists.openembedd= ed.org>
Subject: Re: [OE-core] 2.6 planning proposals and meeting<= /u>

=C2=A0

On Tue, May 1, 2018 at 7:46 AM,= Richard Purdie <richard.purdie@linuxfound= ation.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 l= ayers
> to try some idea, and worked on meta-openembedded, but I've not ha= d 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 spee= d
> 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.

=C2=A0

Yes - please indicate= any areas in the documentation you believe need updated, changed, or added= .=C2=A0 I have been trying to bring things up-to-date in several manuals du= ring the 2.5 process.=C2=A0 So, identifying areas in the 2.5 manual set would be very helpful.=C2=A0 T= o be sure you are viewing 2.5 manuals use the following form for the URL:

=C2=A0 =C2=A0 =C2=A0 = yoctoproject.org/docs/2.5/<manual_folder>/<manual_folder&= gt;.html

=C2=A0 =C2=A0 =C2=A0 = where <manual_folder> is

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 brief-yocto= projectqs

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 bsp-guide

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 overview-ma= nual

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 dev-manual<= u>

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 sdk-manual<= u>

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 profile-man= ual

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 kernel-dev<= u>

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 ref-manual<= u>

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 toaster-man= ual

=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0=C2=A0 bitbake-user-guide

Thanks

Scott

Is ther= e 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.yoctop= roject.org/pipermail/yocto/2018-January/039787.html) at the e= nd of January (last pinged a month ago) and it still has not made it into the manual AFAICT and it has not received any f= eedback.

//Peter=

=C2=A0<= /span>

=C2=A0


--000000000000338e03056b642afa--