From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: "Reyna, David" <david.reyna@windriver.com>,
"AVERY, BRIAN" <brian.avery@intel.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Move Toaster Settings default from Morty to Pyro??
Date: Tue, 18 Apr 2017 11:54:54 +0100 [thread overview]
Message-ID: <1492512894.3632.3.camel@linux.intel.com> (raw)
In-Reply-To: <5E53D14CE4667A45B9A06760DE5D13D0CF6075ED@ALA-MBC.corp.ad.wrs.com>
[-- Attachment #1: Type: text/plain, Size: 2370 bytes --]
On Fri, 2017-04-14 at 04:03 +0000, Reyna, David wrote:
> Hi Joshua and Brian,
>
> It occurs to me that we have an end-of-release task of updating
> “fixtures/poky.xml”, “fixtures/oe-core.xml”, and
> “fixtures/settings.xml” from “Morty” to the next release name, which
> I think is “Pyro” for YP-2.3.
The name for the 2.3 release is pyro. It looks like those files are
indeed usually updated in preparation for the release.
> Is this true? Should I prepare and submit a patch ASAP to bitbake-
> devel?
Please do!
Joshua
> - David
>
> [poky]$ grep -i morty bitbake/lib/toaster/orm/fixtures/*
> bitbake/lib/toaster/orm/fixtures/oe-core.xml: <field
> type="CharField" name="name">morty</field>
> bitbake/lib/toaster/orm/fixtures/oe-core.xml: <field
> type="CharField" name="name">morty</field>
> bitbake/lib/toaster/orm/fixtures/oe-core.xml: <field
> type="CharField" name="description">Openembedded
> Morty</field>
> bitbake/lib/toaster/orm/fixtures/oe-core.xml: <field
> type="CharField" name="branch_name">morty</field>
> bitbake/lib/toaster/orm/fixtures/oe-core.xml: <field
> type="TextField" name="helptext">Toaster will run your builds using
> the tip of the <a href=\"http://cgit.openembedded.org/openembedded
> -core/log/?h=morty\">OpenEmbedded
> Morty</a> branch.</field>
> bitbake/lib/toaster/orm/fixtures/poky.xml: <field type="CharField"
> name="name">morty</field>
> bitbake/lib/toaster/orm/fixtures/poky.xml: <field type="CharField"
> name="branch">morty</field>
> bitbake/lib/toaster/orm/fixtures/poky.xml: <field type="CharField"
> name="name">morty</field>
> bitbake/lib/toaster/orm/fixtures/poky.xml: <field type="CharField"
> name="description">Yocto Project 2.2 "Morty"</field>
> bitbake/lib/toaster/orm/fixtures/poky.xml: <field type="CharField"
> name="branch_name">morty</field>
> bitbake/lib/toaster/orm/fixtures/poky.xml: <field type="TextField"
> name="helptext">Toaster will run your builds using the tip of the
> <a href="http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=mor
> ty">Yocto
> Project Morty branch</a>.</field>
> bitbake/lib/toaster/orm/fixtures/settings.xml: <field
> type="CharField" name="value">morty</field>
> [poky]$
>
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 6727 bytes --]
next prev parent reply other threads:[~2017-04-18 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 4:03 Move Toaster Settings default from Morty to Pyro?? Reyna, David
2017-04-18 10:54 ` Joshua Lock [this message]
2017-04-18 23:06 ` Reyna, David
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=1492512894.3632.3.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=brian.avery@intel.com \
--cc=david.reyna@windriver.com \
--cc=toaster@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.