From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2015.04-rc1 released
Date: Mon, 2 Feb 2015 14:00:12 -0500 [thread overview]
Message-ID: <20150202190012.GQ10826@bill-the-cat> (raw)
Hey all,
I've pushed v2015.04-rc1 out to the repository and tarballs should exist
soon.
The merge window is now closed. I'm going to do my best to keep to the
every two weeks we do an RC thing again this time and continuing to rely
on everyones best judgement about what level of changes they're going to
put into a pull request to me.
With -rc1 out, if things don't have a plan to move to generic board (for
example I saw the series for microblaze) it's time to put up a removal
series and CC anyone still listed as being interested in it.
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/20150202/164777ca/attachment.sig>
next reply other threads:[~2015-02-02 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 19:00 Tom Rini [this message]
2015-02-02 22:03 ` [U-Boot] [ANN] U-Boot v2015.04-rc1 released Sinan Akman
2015-02-02 22:14 ` 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=20150202190012.GQ10826@bill-the-cat \
--to=trini@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.