From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [ANN] U-Boot v2020.04-rc4 released
Date: Mon, 30 Mar 2020 19:31:00 -0400 [thread overview]
Message-ID: <20200330233100.GS27133@bill-the-cat> (raw)
Hey all,
So, I've gotten out of the habit of tagging rcs on cycle. This month I
have been taking in changes sparingly and I'm not concerned that things
have gone in that wouldn't have, if I had tagged -rc4/rc5 on schedule.
Things have been going to the -next branch as expected, and I think
that will work out when things open up for v2020.07
So here now is -rc4 and I plan to make the final release on April 6th,
as scheduled. Thanks all and stay safe out there!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200330/c8abb8b2/attachment.sig>
next reply other threads:[~2020-03-30 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 23:31 Tom Rini [this message]
2020-04-01 11:54 ` [ANN] U-Boot v2020.04-rc4 released Andy Shevchenko
2020-04-01 11:59 ` Andy Shevchenko
2020-04-01 12:45 ` Antwort: " Wolfgang Wallner
2020-04-01 13:38 ` Andy Shevchenko
2020-04-01 13:54 ` Andy Shevchenko
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=20200330233100.GS27133@bill-the-cat \
--to=trini@konsulko.com \
--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