From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] v2013.01-rc3 out
Date: Thu, 10 Jan 2013 14:49:43 -0700 [thread overview]
Message-ID: <20130110214943.GA10647@bill-the-cat> (raw)
Hey all,
As a reminder, we're scheduled for v2013.01 on the 15th. I've pushed
out v2013.01-rc3 now. I still expect:
- At least one more u-boot-arm PR
- Any other outstand bug fixes
I saw there was a request for an m68k change to come in from a
developer, Jason can you review and pass along please? It is assigned
to you in patchwork. And I suspect there's a few more bugfixes out
there we need to handle (I know of 2 different one for IGEP boards).
Please remind me here if there's something else that needs reviewing and
going in, thanks!
--
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/20130110/a1a3e690/attachment.pgp>
next reply other threads:[~2013-01-10 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 21:49 Tom Rini [this message]
2013-01-11 7:15 ` [U-Boot] [STATUS] v2013.01-rc3 out Lukasz Majewski
2013-01-11 13:27 ` Marek Vasut
2013-01-11 14:49 ` Jens Scharsig
2013-01-14 7:33 ` Nikita Kiryanov
2013-01-14 12:47 ` 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=20130110214943.GA10647@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