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
Subject: [U-Boot] [ANN] U-Boot v2020.01-rc4 released
Date: Mon, 2 Dec 2019 22:10:56 -0500	[thread overview]
Message-ID: <20191203031056.GK15966@bill-the-cat> (raw)

Hey all,

It's release day and here is v2020.01-rc4.  Yes, I'm still working on
fixing all of the issues that pop up as I get the MTD clean-up series
ready to go.  In fact, what I need to do at this point is grab the
handful of size reduction patches that this has shown are worthwhile,
then I can do the MTD series.  Then we're down to just fixing up
misconversions where things got turned off.

Once again, for a changelog, 
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can
put them in the merge commit.

I'm planning on doing -rc5 on December 23rd with the release scheduled
on January 6th.  Thanks all!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191202/e1321951/attachment.sig>

             reply	other threads:[~2019-12-03  3:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03  3:10 Tom Rini [this message]
     [not found] ` <73b453a4-ed9c-3177-6623-0ce716cc31a8@microchip.com>
2019-12-03 11:55   ` [U-Boot-Custodians] [ANN] U-Boot v2020.01-rc4 released Eugen.Hristev at microchip.com
2019-12-03 14:30   ` Tom Rini
2019-12-03 16:45 ` Joe Hershberger
2019-12-03 17:05   ` Tom Rini
2019-12-03 20:56     ` Joe Hershberger
2019-12-03 21:03       ` Tom Rini
2019-12-03 16:52 ` Simon Glass
2019-12-03 17:00   ` Marek Vasut
2019-12-03 17:07     ` Tom Rini
2019-12-03 17:20       ` Simon Glass
2019-12-03 17:41         ` Tom Rini

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=20191203031056.GK15966@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