From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: Google Summer of Code
Date: Mon, 25 Feb 2008 19:34:07 -0500 [thread overview]
Message-ID: <47C35E7F.10907@balister.org> (raw)
In-Reply-To: <47C32843.8010302@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
Jacob Thebault-Spieker wrote:
> I can see how my idea may not fit openembedded exactly. I guess I just
> decided to try here first, as OE is not only the build-system, but also
> the base for many distros, most of which work closely with OE. If OE is
> not the right place, I will most definitely check with Angstrom, I just
> thought I should check here first. Thanks for the input.
What are the deadlines for SoC? I'm not sure if we will have the
infrastructure in place to do direct OE SoC projects this year. I'll
ping the board though.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-02-26 0:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 19:15 Google Summer of Code Jacob Thebault-Spieker
2008-02-25 20:36 ` Leon Woestenberg
2008-02-25 20:42 ` Jacob Thebault-Spieker
2008-02-26 0:34 ` Philip Balister [this message]
2008-02-26 5:27 ` Jacob Thebault-Spieker
2008-02-26 10:41 ` Paul Sokolovsky
2008-02-25 20:40 ` Jelle de Jong
2008-02-26 0:07 ` Erik Hovland
-- strict thread matches above, loose matches on Subject: below --
2017-02-20 5:29 Matthew Sedam
2016-03-13 12:24 Shreedhar Manek
[not found] <48CF5AC71E61DB46B70D0F388054EFFD12D0DC32@VAL-E-02.valcartier.drdc-rddc.gc.ca>
2013-04-10 21:53 ` Jérémie Galarneau
[not found] ` <CA+jJMxtP+n274AhsXQ23TXYPo8UsXtShjYxwJwwO69e=N1nbnQ@mail.gmail.com>
2013-04-11 13:20 ` Thibault, Daniel
2013-04-09 15:21 Thibault, Daniel
2013-02-26 13:35 Ognjen Ikovic
2007-03-03 15:10 Benjamin Prosnitz
2007-03-04 8:55 ` Avi Kivity
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=47C35E7F.10907@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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.