From: Joe MacDonald <joe@deserted.net>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH 1/3] snort: add recipe
Date: Mon, 23 Sep 2013 14:22:02 -0400 [thread overview]
Message-ID: <20130923182159.GA30829@deserted.net> (raw)
In-Reply-To: <10075581.zIxvIPmXvh@helios>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
Hey Paul,
[Re: [oe] [meta-networking][PATCH 1/3] snort: add recipe] On 13.09.23 (Mon 18:56) Paul Eggleton wrote:
> All,
>
> 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.
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-09-23 18:22 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 [this message]
2013-09-24 17:16 ` Paul Eggleton
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=20130923182159.GA30829@deserted.net \
--to=joe@deserted.net \
--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