From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Joe MacDonald <joe@deserted.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH 1/3] snort: add recipe
Date: Tue, 24 Sep 2013 18:16:33 +0100 [thread overview]
Message-ID: <62747590.0CPS7u3973@helios> (raw)
In-Reply-To: <20130923182159.GA30829@deserted.net>
Hi Joe,
On Monday 23 September 2013 14:22:02 Joe MacDonald wrote:
> [Re: [oe] [meta-networking][PATCH 1/3] snort: add recipe] On 13.09.23 (Mon
> 18:56) Paul Eggleton wrote:
> >
> > I'm a bit confused; is this recipe supposed to be going into
> > meta-networking or meta-security? Because patches have been sent
> > recently to add it to both.
>
> I had mentioned that I would accept snort into meta-networking if it
> wasn't a good fit for meta-security since it was something I'd started
> working on integrating anyway a while back. I assumed that was the case
> since it was sent to the list for meta-networking today.
>
> I don't think we need copies in both places, though, and since it was
> first aimed at meta-security, if it gets merged there, I won't merge it
> here.
>
> Hopefully nothing I've said here contradicts what the meta-security
> maintainers would want to see.
I would have thought it would go into meta-security myself; but ultimately
it's up to you and Saul really. I just wanted to make sure we didn't somehow
end up with it in both layers since we have patches for adding it to both.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-09-24 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 9:06 [meta-networking][PATCH 1/3] snort: add recipe b40290
2013-09-23 16:58 ` Joe MacDonald
2013-09-23 17:13 ` Joe MacDonald
2013-09-23 17:56 ` Paul Eggleton
2013-09-23 18:22 ` Joe MacDonald
2013-09-24 17:16 ` Paul Eggleton [this message]
2013-09-24 18:10 ` Joe MacDonald
-- strict thread matches above, loose matches on Subject: below --
2013-10-16 7:11 [meta-networking][PATCH 1/3] snort : " b40290
2013-10-16 8:43 ` Koen Kooi
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=62747590.0CPS7u3973@helios \
--to=paul.eggleton@linux.intel.com \
--cc=joe@deserted.net \
--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.