From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mauno Niko <niko.mauno@vaisala.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Missing git tags for latest Morty release?
Date: Mon, 19 Feb 2018 15:28:17 +0000 [thread overview]
Message-ID: <1519054097.24236.247.camel@linuxfoundation.org> (raw)
In-Reply-To: <ddc7757a-ea92-9841-a521-47d9b68b2de6@vaisala.com>
On Mon, 2018-02-19 at 12:15 +0000, Mauno Niko wrote:
> Even <https://wiki.yoctoproject.org/wiki/Releases> states "Current
> Version" is "2.2.3" for Codename Morty, associated "yocto-2.2.3",
> "morty-16.0.3" tags do not seem to exist, could someone please create
> those?
2.2.3 is actually undergoing QA testing at the moment and has not been
released yet but has been built. I suspect someone updated the wiki
prematurely.
Cheers,
Richard
prev parent reply other threads:[~2018-02-19 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 12:15 Missing git tags for latest Morty release? Mauno Niko
2018-02-19 15:28 ` Richard Purdie [this message]
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=1519054097.24236.247.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=niko.mauno@vaisala.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox