From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] thttpd: Port thttpd from oe-classic.
Date: Fri, 19 Oct 2012 08:10:35 -0400 [thread overview]
Message-ID: <20121019121035.GA5000@windriver.com> (raw)
In-Reply-To: <168838562.YJes5mSNF6@helios>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
[Re: [oe] [meta-oe][PATCH] thttpd: Port thttpd from oe-classic.] On 12.10.19 (Fri 11:44) Paul Eggleton wrote:
> On Tuesday 18 September 2012 11:39:24 Joe MacDonald wrote:
> > On Tue, Sep 18, 2012 at 4:38 AM, Koen Kooi <koen@dominion.thruhere.net>
> wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Op 17-09-12 20:18, Franklin S. Cooper Jr schreef:
> > >> * Port thttpd recipe from oe-classic to meta-oe.
> > >
> > > It should go into meta-networking
> >
> > Agreed. Once it's been LSB'd, please put the recipe in
> > meta-networking/recipes-daemons/
>
> meta-networking or meta-webserver?
I'd originally had it on my proposed meta-networking list, but that
pre-dated the meta-webserver layer. I'm okay with either location, but
there does seem to be a natural fit with meta-webserver, now that I
think about it.
--
Joe MacDonald, Sr. Member of Technical Staff, Linux Products Group, Wind River
direct 613.270.5750 mobile 613.291.7421 fax 613.592.2283
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2012-10-23 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 18:18 [meta-oe][PATCH] thttpd: Port thttpd from oe-classic Franklin S. Cooper Jr
2012-09-18 8:38 ` Koen Kooi
2012-09-18 15:39 ` Joe MacDonald
2012-10-19 10:44 ` Paul Eggleton
2012-10-19 12:10 ` Joe MacDonald [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=20121019121035.GA5000@windriver.com \
--to=joe.macdonald@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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