Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Zongchun YU <b40527@freescale.com>
To: 'Martin Jansa' <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] tcpdump, tcpreplay:relocate tcpdump and add tcpreplay recipe
Date: Thu, 7 Nov 2013 11:42:22 +0800	[thread overview]
Message-ID: <003701cedb6b$5f7bde20$1e739a60$@com> (raw)
In-Reply-To: <CA+chaQcpPKUwM6LfuKvvStDLvRYBEeBuPmHnxXuJdEee=zv3tA@mail.gmail.com>

>Please use -M to get smaller diff.

Hello Martin.

 

Thanks for your reminder. I have send one new patch to you and the mail list. 

But I don’t know why the patch is rejected by the mail list? It is ok before.

If you have suggestion. Please reply to me directly.

 

Best Regards

Zongchun



      reply	other threads:[~2013-11-07  3:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06  5:40 [meta-networking][PATCH] tcpdump, tcpreplay:relocate tcpdump and add tcpreplay recipe Zongchun.Yu
2013-11-06 13:06 ` Martin Jansa
2013-11-07  3:42   ` 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='003701cedb6b$5f7bde20$1e739a60$@com' \
    --to=b40527@freescale.com \
    --cc=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox