From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Cc: B29882@freescale.com, B19537@freescale.com
Subject: Re: [meta-oe v4 ] inetutils : Update to 1.9.1 * There are difference spaces between inetutils-1.8/COPYING and inetutils-1.9.1/COPYING, so md5sum is changed.6
Date: Thu, 15 Nov 2012 13:50:10 +0000 [thread overview]
Message-ID: <2449434.J2bi9dLU3a@helios> (raw)
In-Reply-To: <1352975896-14628-1-git-send-email-b40290@freescale.com>
On Thursday 15 November 2012 18:38:16 Chunrong Guo wrote:
> Signed-off-by: Chunrong Guo <b40290@freescale.com>
> ---
Somehow the commit message got mangled here - could you please resend? Also,
given you are going to be resending and the recipe is being moved to meta-
networking can you use the prefix "meta-networking" instead of "meta-oe"?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-11-15 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 10:38 [meta-oe v4 ] inetutils : Update to 1.9.1 * There are difference spaces between inetutils-1.8/COPYING and inetutils-1.9.1/COPYING, so md5sum is changed.6 Chunrong Guo
2012-11-15 13:50 ` Paul Eggleton [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=2449434.J2bi9dLU3a@helios \
--to=paul.eggleton@linux.intel.com \
--cc=B19537@freescale.com \
--cc=B29882@freescale.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