From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Next steps
Date: Thu, 13 Sep 2012 10:33:29 -0700 [thread overview]
Message-ID: <505218E9.6030301@ti.com> (raw)
In-Reply-To: <5051D359.4060000@gmail.com>
On 09/13/2012 05:36 AM, Andreas Bie?mann wrote:
> Dear Tom Rini,
> Dear Albert Aribaud,
>
> On 12.09.2012 17:15, Tom Rini wrote:
>> Hey all,
>>
>> I know some of you have known me for ages, and some of you only as long
>> as my jaunt back into U-Boot over the last year. Rather than talk
>> myself up, I'd like to go with actions to let everyone know you're in
>> good hands.
>>
>> I'd like to ask a few things of the community right now. If you're a
>> custodian and have an outstanding pull request (I see a few on the
>> mailing list right now even), please assign it to me in patchwork and
>> shoot me a private email with a link too. If you aren't in patchwork
>> please sign up. I know it's imperfect and we've talked about how to
>> make something better, but it's the tool we have today.
>
> I just sent my pull request for u-boot-avr32 and have some more fixes
> for u-boot-atmel which will require at least one more pull request for
> you Albert.
> Additional to theses fixes there are two patches missing which should go
> through Mikes sf branch [1].
> Is it Ok to pick these two patches through u-boot-atmel if Mike is not
> responding until this Weekend?
> I will then send another pull request for u-boot-atmel/master presumably
> Saturday the 15th, is this Ok for you?
Unless Albert says otherwise, I imagine waiting until Mike picks things
up this weekend will be fine.
--
Tom
prev parent reply other threads:[~2012-09-13 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 15:15 [U-Boot] Next steps Tom Rini
2012-09-13 12:36 ` Andreas Bießmann
2012-09-13 17:33 ` 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=505218E9.6030301@ti.com \
--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.