From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: netperf in meta-networking
Date: Fri, 30 Nov 2012 11:54:11 -0500 [thread overview]
Message-ID: <20121130165410.GQ6912@windriver.com> (raw)
In-Reply-To: <20121130163410.GP6912@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
[Re: [oe] netperf in meta-networking] On 12.11.30 (Fri 11:34) Joe MacDonald wrote:
> [netperf in meta-networking] On 12.11.30 (Fri 10:18) Mark Hatle wrote:
>
> > So anyway, my suggestion is to simply change the value of the flag.
[...]
> So I'm inclined to agree, this sounds like the definition of
> non-commercial above to me.
Updated. Thanks for the heads-up.
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-11-30 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 16:18 netperf in meta-networking Mark Hatle
2012-11-30 16:34 ` Joe MacDonald
2012-11-30 16:54 ` Joe MacDonald [this message]
2012-11-30 16:55 ` Paul Eggleton
2012-11-30 17:11 ` Mark Hatle
2012-11-30 17:56 ` Joe MacDonald
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=20121130165410.GQ6912@windriver.com \
--to=joe.macdonald@windriver.com \
--cc=mark.hatle@windriver.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