From: Zongchun YU <b40527@freescale.com>
To: 'Otavio Salvador' <otavio@ossystems.com.br>,
'OpenEmbedded Devel List'
<openembedded-devel@lists.openembedded.org>
Cc: 'Zongchun Yu' <Zongchun.Yu@freescale.com>
Subject: Re: [meta-oe][meta-networking][PATCHv2] tcpdump, tcpreplay:relocate tcpdump and add tcpreplay recipe
Date: Tue, 26 Nov 2013 10:58:08 +0800 [thread overview]
Message-ID: <005701ceea53$57670ec0$06352c40$@com> (raw)
In-Reply-To: <CAP9ODKo9KDmcMMG3ay8E-nTzpyyRK_tAa3Aq5-MhfF4pO-+rOQ@mail.gmail.com>
>Please split the patch in two, one for the move for meta-networking and
another to add the tcpreplay utility.
Thanks for your comments. I have resent the patches. Please review.
prev parent reply other threads:[~2013-11-26 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 8:00 [meta-oe][meta-networking][PATCHv2] tcpdump, tcpreplay:relocate tcpdump and add tcpreplay recipe b40527
2013-11-25 14:11 ` Otavio Salvador
2013-11-26 2:58 ` Zongchun YU [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='005701ceea53$57670ec0$06352c40$@com' \
--to=b40527@freescale.com \
--cc=Zongchun.Yu@freescale.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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