From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Ping on pending U-Boot patches
Date: Fri, 25 Aug 2006 11:16:43 -0500 [thread overview]
Message-ID: <44EF226B.9010501@orkun.us> (raw)
In-Reply-To: <20060824225815.58676353A61@atlas.denx.de>
Wolfgang Denk wrote:
> Dear Toluny,
>
> in message <44EE0EAF.8000301@orkun.us> you wrote:
>
>> Can you provide the status of the following two patches that I've
>> submitted early April? I appreciate if you can apply them if there are
>> no objections.
>>
>
> A look at the current CHANGELOG will show you how far I am: start
> December 2005. I need more time. Sorry.
>
> Best regards,
>
> Wolfgang Denk
>
>
How about some delegation to assist you in this severe backlog? ;) Maybe
Stefan can take some of your load on this matter. The files affected
were low level CPU support apparently done by him and he seems to have
commit rights over there...
Best regards,
Tolunay
next prev parent reply other threads:[~2006-08-25 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 20:40 [U-Boot-Users] Ping on pending U-Boot patches Tolunay Orkun
2006-08-24 22:58 ` Wolfgang Denk
2006-08-25 16:16 ` Tolunay Orkun [this message]
2006-08-27 11:12 ` Stefan Roese
2006-10-11 22:34 ` Tolunay Orkun
2006-10-12 5:36 ` Stefan Roese
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=44EF226B.9010501@orkun.us \
--to=listmember@orkun.us \
--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