From: Ryan Eatmon <reatmon@ti.com>
To: Denys Dmytriyenko <denis@denix.org>, <meta-arago@lists.yoctoproject.org>
Cc: Denys Dmytriyenko <denys@konsulko.com>
Subject: Re: [meta-arago] [master/kirkstone][PATCH] arago.conf: bump distro version
Date: Wed, 8 Nov 2023 08:13:20 -0600 [thread overview]
Message-ID: <26f27cb3-96c1-4316-be7d-fee8e9e59e21@ti.com> (raw)
In-Reply-To: <20231108000329.3065800-1-denis@denix.org>
On 11/7/2023 6:03 PM, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko <denys@konsulko.com>
>
> A bit arbitrary, but it seems like a good point in time to bump Arago Distro
> version, since things are relatively stable currently and to coincide with
> the Yocto Project Nanbield release.
>
> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Acked-by: Ryan Eatmon <reatmon@ti.com>
> ---
> meta-arago-distro/conf/distro/arago.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-arago-distro/conf/distro/arago.conf b/meta-arago-distro/conf/distro/arago.conf
> index 8232ca27..83b1a18a 100644
> --- a/meta-arago-distro/conf/distro/arago.conf
> +++ b/meta-arago-distro/conf/distro/arago.conf
> @@ -1,6 +1,6 @@
> # Name and version of the distribution
> DISTRO_NAME = "Arago"
> -DISTRO_VERSION = "2023.04"
> +DISTRO_VERSION = "2023.10"
> DISTRO_FEED_URI ?= "http://lcpd.itg.ti.com"
> BUILD_VARIANT = "${@['prod','rt','systest'][int(d.getVar('ARAGO_RT_ENABLE'))+int(d.getVar('ARAGO_SYSTEST_ENABLE'))*2]}"
> TISDK_VERSION ?= "live"
--
Ryan Eatmon reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc. - LCPD - MGTS
prev parent reply other threads:[~2023-11-08 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 0:03 [master/kirkstone][PATCH] arago.conf: bump distro version Denys Dmytriyenko
2023-11-08 14:13 ` Ryan Eatmon [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=26f27cb3-96c1-4316-be7d-fee8e9e59e21@ti.com \
--to=reatmon@ti.com \
--cc=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-arago@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).