From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Cc: u-boot-custodians@lists.denx.de, u-boot-board-maintainers@lists.denx.de
Subject: [ANN] U-Boot v2023.10-rc1 released
Date: Tue, 25 Jul 2023 17:20:19 -0400 [thread overview]
Message-ID: <20230725212019.GE3630934@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Hey all,
So I'm a day late with -rc1 because as may have been noticed, things
went a bit wrong at the end of the day yesterday when I hoped to squeeze
in a few of the last things that needed to come in. I may or may not
have learned my lesson, but here's -rc1 now. There's still some
outstanding things to come in by -rc2, both in my own queue and
hopefully a few other custodian trees too.
In terms of a changelog,
git log --merges v2023.07..v2023.10-rc1
contains what I've pulled but as always, better PR messages and tags
will provide better results here.
I'm going to try and stay on schedule now and that means the rest of the
rcs every other Monday, and with final release on October 2nd, 2023.
Thanks all!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
reply other threads:[~2023-07-25 21:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230725212019.GE3630934@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot-board-maintainers@lists.denx.de \
--cc=u-boot-custodians@lists.denx.de \
--cc=u-boot@lists.denx.de \
/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