From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Weekly status
Date: Tue, 18 Sep 2012 08:03:26 -0700 [thread overview]
Message-ID: <20120918150326.GH14937@bill-the-cat> (raw)
In-Reply-To: <20120917143132.GA31809@bill-the-cat>
On Mon, Sep 17, 2012 at 07:31:32AM -0700, Tom Rini wrote:
> Hey all,
>
> I had intended to send this last thing Friday but it slipped my mind.
> But with my intention to do -rc1 this Friday, this works too. That
> said...
>
> Here's where I'm at so far:
> - Locally, I believe I have all outstanding pull requets queued up and
> MAKEALL'd when there's an ELDK toolchain.
> - Working out the access issues with Detlev.
We've worked this out today (as the batch of applied merge request
emails hint at). I'm looking for any further pull requests I missed
then moving onto individual patches (didn't want to queue up too much in
the tree before pushing). Looking on-track for Friday.
--
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/20120918/3f71bc89/attachment.pgp>
prev parent reply other threads:[~2012-09-18 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 14:31 [U-Boot] Weekly status Tom Rini
2012-09-17 17:50 ` Marek Vasut
2012-09-18 15:03 ` Tom Rini [this message]
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=20120918150326.GH14937@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