From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2016.01-rc1 released
Date: Mon, 16 Nov 2015 20:41:04 -0500 [thread overview]
Message-ID: <20151117014104.GU8060@bill-the-cat> (raw)
Hey all,
I've pushed v2016.01-rc1 out to the repository and tarballs should exist
soon.
The merge window is now closed. I too an extra week to tag things since
I wanted a few more things to land and then they did. This feels like a
good solid -rc1 and we've had some nice updates come in and progress
being made on various fronts.
And as is often the case, there's a big bunch of stuff I need to go and
pick up still and merge. And this time I'm also going to submit things
to coverity for sandbox. If you think you'll have time to explore the
bug reports please request to join the project.
As always, if anything is broken please speak up.
Thanks all!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151116/da492d89/attachment.sig>
next reply other threads:[~2015-11-17 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 1:41 Tom Rini [this message]
2015-11-17 8:40 ` [U-Boot] [ANN] U-Boot v2016.01-rc1 released Wolfgang Denk
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=20151117014104.GU8060@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