From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] v2013.10-rc1
Date: Mon, 19 Aug 2013 18:02:26 -0400 [thread overview]
Message-ID: <20130819220226.GC17559@bill-the-cat> (raw)
Hey all,
I've put v2013.10-rc1 out, and I hope Detlev can get the tarball
uploaded soon.
We've got a lot of changes in here, including the SPDX license
conversion. I'd like to ask folks to test things and let me know what's
in patchwork and should be applied, but hasn't been just yet.
Thanks all!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130819/0fe3cee2/attachment.pgp>
next reply other threads:[~2013-08-19 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 22:02 Tom Rini [this message]
2013-08-20 4:14 ` [U-Boot] [ANN] v2013.10-rc1 Heiko Schocher
2013-08-20 8:52 ` Stefano Babic
2013-08-20 15:56 ` Tom Rini
2013-08-21 10:42 ` Detlev Zundel
-- strict thread matches above, loose matches on Subject: below --
2013-09-02 18:24 Tom Rini
2013-09-02 18:45 ` 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=20130819220226.GC17559@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox