From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] obtaining linux kernel from git
Date: Thu, 20 May 2010 10:25:03 +0100 [thread overview]
Message-ID: <4BF4FFEF.1030704@carallon.com> (raw)
In-Reply-To: <1274216561.7985.1.camel@ufo>
On 18/05/2010 22:02, Cristi Magherusan wrote:
> Hi,
>
> Any news about this?
>
I have a couple of patches in my tree. Once 10.05 is out I will look at
posting them to the list.
Will
> I'm interested in this feature and I would really like to see it merged.
> What else needs to be done in order to achieve this goal?
>
> Regards,
> Cristi
>
>
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
prev parent reply other threads:[~2010-05-20 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 20:00 [Buildroot] obtaining linux kernel from git William Wagner
2010-01-11 21:50 ` Grant Likely
2010-01-12 1:42 ` Michael S. Zick
2010-01-12 10:01 ` William Wagner
2010-05-18 21:02 ` Cristi Magherusan
2010-05-20 9:25 ` William Wagner [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=4BF4FFEF.1030704@carallon.com \
--to=will_wagner@carallon.com \
--cc=buildroot@busybox.net \
/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