public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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.01-rc1 released
Date: Mon, 7 Nov 2022 15:30:24 -0500	[thread overview]
Message-ID: <20221107203024.GL6335@bill-the-cat> (raw)

[-- Attachment #1: Type: text/plain, Size: 634 bytes --]

Hey all,

I'm behind schedule, yes. By the time I noticed I had missed doing -rc1
it was nearly time for -rc2, so I decided to just wait until now. Extra
long merge window. Anyhow, there's a lot in here and testing on as many
platforms as possible is much appreciated.

In terms of a changelog, 
git log --merges v2022.10..v2023.01-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 the correct schedule now and that means the
rest of the rcs every other Monday, and with final release on January
9th, 2023.  Thanks all!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

                 reply	other threads:[~2022-11-07 20:30 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=20221107203024.GL6335@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