All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Proposal: Creating meta-networking
Date: Mon, 23 Jul 2012 20:09:41 -0400	[thread overview]
Message-ID: <20120724000940.GA4014@windriver.com> (raw)
In-Reply-To: <500D4B57.3020800@mentor.com>

[[oe]  Proposal: Creating meta-networking] On 12.07.23 (Mon 17:02) Firago Alexey wrote:

> Hi all,
> 
> On 6/15/2012 8:15 AM, Joe MacDonald wrote:
> >We've been talking about this on-and-off at Wind River for a while now,
> >but it now seems like a reasonable time to bring a proposal to the OE
> >community at large.  We're thinking about creating a new layer to house
> >recipes, etc.  for networking packages.
> >...
> >So what does everyone think?  Awesome idea?  Terrible idea?  (Hopefully)
> >something in between?  All feedback is welcome.
> 
> I think creating software support layer for network related packages
> is good idea.
> We've updated some of the recipes from OE Classic mentioned above
> for our projects at Mentor Graphics.
> We've been thinking to place these updated recipes in meta-oe layer.
> But I think now that separate layer like meta-networking
> would be much more suitable place.  Also we've created some new
> packages like mipv6-umip or multipath-tools
> that are good candidates for being placed in meta-networking.
> 
> So, I suggest Mentor Graphics would contribute to meta-networking.

That's great to hear!  As you can probably tell there's been not much
activity on this front for the last week or so, but I anticipate getting
back at it in the next day or two.  I'll be sure to copy the list on
anything of interest.

-- 
Joe MacDonald, Sr. Member of Technical Staff, Linux Products Group, Wind River
direct 613.270.5750     mobile 613.291.7421     fax 613.592.2283



  reply	other threads:[~2012-07-24  0:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 13:02 Proposal: Creating meta-networking Firago Alexey
2012-07-24  0:09 ` Joe MacDonald [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-23 12:57 Firago Alexey
2012-06-15 15:15 Joe MacDonald
2012-06-15 15:42 ` Khem Raj
2012-06-15 18:08   ` Otavio Salvador
2012-06-15 18:55     ` Andrei Gherzan
2012-06-15 19:55       ` Philip Balister
2012-06-16 17:10         ` Joe MacDonald
2012-06-16 17:36         ` Marko Lindqvist
2012-06-16 17:45           ` Otavio Salvador
     [not found] ` <1442756.zsKFTug4Rk@helios>
     [not found]   ` <20120712195752.GN3293@windriver.com>
     [not found]     ` <38351001.3KzA0t96MO@helios>
2012-07-13 16:03       ` Koen Kooi
2012-07-13 16:15         ` Paul Eggleton
2012-07-16  7:16           ` Martin Jansa
2012-07-16 23:15       ` Paul Eggleton
2012-08-22 18:20 ` Christopher Larson
2012-08-22 18:59   ` Joe MacDonald
2012-08-22 19:22     ` Chris Larson
2012-08-22 19:37       ` Joe MacDonald
2012-08-22 19:41         ` Joe MacDonald
2012-08-23  6:22       ` Koen Kooi
2012-08-23 14:54         ` Joe MacDonald

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=20120724000940.GA4014@windriver.com \
    --to=joe.macdonald@windriver.com \
    --cc=openembedded-devel@lists.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.