From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH v2][meta-networking] tcpslice: add recipe under tcpdump
Date: Tue, 2 Sep 2014 08:19:45 -0400 [thread overview]
Message-ID: <20140902121944.GE7949@mentor.com> (raw)
In-Reply-To: <54052F3C.6090006@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
[Re: [oe] [PATCH v2][meta-networking] tcpslice: add recipe under tcpdump] On 14.09.02 (Tue 10:45) Rongqing Li wrote:
>
>
> On 07/30/2014 03:25 PM, Martin Jansa wrote:
> >On Wed, Jul 30, 2014 at 10:22:41AM +0800,rongqing.li@windriver.com wrote:
> >>>From: Roy Li<rongqing.li@windriver.com>
> >>>
> >>>tcpslice is a tool for extracting parts of a tcpdump packet trace,
> >>>so put it under tcpdump dir
> >>>
> >>>Signed-off-by: Roy Li<rongqing.li@windriver.com>
> >>>---
>
>
> Hi Martin:
>
> I see this recipes has been merged into master-next for a long time,
> Could you cherry-pick it to master?
I had asked for some kind of clarification on the license for tcpslice.
I didn't notice a follow-up on it yet, did you get a chance to check
into it?
I don't think anyone has any concern about the stability of the package
itself, though, if we'd had some kind of response on the license
question I had I would've merged it long ago.
-J.
>
>
> -Roy
>
>
> --
> Best Reagrds,
> Roy | RongQing Li
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 501 bytes --]
next prev parent reply other threads:[~2014-09-02 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 2:22 [PATCH v2][meta-networking] tcpslice: add recipe under tcpdump rongqing.li
2014-07-30 7:25 ` Martin Jansa
2014-07-30 7:29 ` Rongqing Li
2014-09-02 2:45 ` Rongqing Li
2014-09-02 12:19 ` Joe MacDonald [this message]
2014-09-03 0:44 ` Rongqing Li
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=20140902121944.GE7949@mentor.com \
--to=joe_macdonald@mentor.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.