From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Scott Rifenbark <srifenbark@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: 2.6 migration guide
Date: Mon, 05 Nov 2018 16:32:26 +1300 [thread overview]
Message-ID: <4820003.uEWOQMMmpA@localhost.localdomain> (raw)
In-Reply-To: <CAFNP8OvFy2n7SMe5de66EcdM3URFm-b+dpcqS09hW0CMa9rNaA@mail.gmail.com>
On Wednesday, 31 October 2018 11:06:31 AM NZDT Scott Rifenbark wrote:
> I have an initial section at
> https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,
> which is based on Richard's input. I am sure there are more items.
OK, so I have removed Richard's items from the wiki page (since they're now
in the manual) and added items I have gathered from reviewing all of the
git commits in the release. Let me know if you need clarification on anything
- everyone else, let us know if I missed or messed up something.
https://wiki.yoctoproject.org/wiki/FutureMigrationGuide
BTW I think the section on postinstalls (from Richard's input) is a little terse
and needs expansion - most importantly it needs to describe what actions the
user might need to take. I'll take care of this on review if nobody else does.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2018-11-05 3:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 21:14 2.6 migration guide Paul Eggleton
2018-10-30 22:06 ` Scott Rifenbark
2018-10-31 7:15 ` Robert Berger
2018-10-31 15:33 ` [yocto] " Scott Rifenbark
2018-10-31 15:33 ` Scott Rifenbark
2018-10-31 15:50 ` [yocto] " Scott Rifenbark
2018-10-31 15:50 ` Scott Rifenbark
2018-10-31 16:01 ` [yocto] " Bas Mevissen
2018-10-31 16:01 ` Bas Mevissen
2018-10-31 16:56 ` [yocto] " Scott Rifenbark
2018-10-31 16:56 ` Scott Rifenbark
2018-11-02 15:10 ` Peter Kjellerstedt
2018-11-02 15:10 ` [OE-core] " Peter Kjellerstedt
2018-11-02 15:48 ` Scott Rifenbark
2018-11-02 15:48 ` [OE-core] " Scott Rifenbark
2018-11-05 3:32 ` Paul Eggleton [this message]
2018-11-08 22:41 ` [yocto] " Paul Eggleton
2018-11-08 22:41 ` Paul Eggleton
2018-11-08 22:50 ` [yocto] " Paul Eggleton
2018-11-08 22:50 ` [OE-core] " Paul Eggleton
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=4820003.uEWOQMMmpA@localhost.localdomain \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=srifenbark@gmail.com \
--cc=yocto@yoctoproject.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.