From: Paul Barker <paul@betafive.co.uk>
To: Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: yocto jethro failed on gettext-native
Date: Wed, 02 May 2018 21:36:19 +0100 [thread overview]
Message-ID: <1525293379.1343784.1358733424.3328B6FF@webmail.messagingengine.com> (raw)
In-Reply-To: <CAGAf8LziVYUN6ZK622JURBer5CUHGTKQvx9t53Ut7NX9JO9-wA@mail.gmail.com>
On Wed, 25 Apr 2018, at 21:55, Zoran Stojsavljevic wrote:
> > Jethro doesn't support Yocto 16.* because it is very old (released 2015...)...
>
> Now, I must admit, I have learned something new. Never gave any
> consideration to these releases: example: Pyro 17.0.3.
>
> But now I understand: it has direct link with Ubuntu 17... Even, YOCTO
> Pyro, as given example, can be substituted with Ubuntu 17.04?! Wow...
>
> Every day in every way, I'm progressing more and more! ;-)
>
You seem to be a bit confused here by the fact that the poky version number lined up with the year in 2017. See https://wiki.yoctoproject.org/wiki/Releases for some context.
--
Paul Barker
Beta Five Ltd
next prev parent reply other threads:[~2018-05-02 20:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 15:03 yocto jethro failed on gettext-native Oliver Graute
2018-04-25 17:49 ` Zoran Stojsavljevic
[not found] ` <CAEv37YsacVBmZXtShCij9OxkXmQpUX92QnS=tg_ESO_0NkT3ow@mail.gmail.com>
2018-04-25 18:27 ` Zoran Stojsavljevic
2018-04-25 19:36 ` Oliver Graute
2018-04-25 19:50 ` Burton, Ross
2018-04-25 20:49 ` Randy MacLeod
2018-04-25 20:55 ` Zoran Stojsavljevic
2018-04-25 20:58 ` Zoran Stojsavljevic
2018-05-02 20:36 ` Paul Barker [this message]
2018-05-03 3:29 ` Zoran Stojsavljevic
2018-04-26 4:07 ` Andre McCurdy
2018-04-26 15:53 ` Oliver Graute
2018-04-26 17:33 ` Zoran Stojsavljevic
2018-04-27 6:19 ` Oliver Graute
2018-04-27 9:25 ` Zoran Stojsavljevic
2018-04-27 12:04 ` Philip Balister
2018-04-27 13:27 ` Zoran Stojsavljevic
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=1525293379.1343784.1358733424.3328B6FF@webmail.messagingengine.com \
--to=paul@betafive.co.uk \
--cc=yocto@yoctoproject.org \
--cc=zoran.stojsavljevic@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 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.