From: Panu Matilainen <pmatilai@redhat.com>
To: "Wiles, Keith" <keith.wiles@intel.com>,
Matthew Hall <mhall@mhcomputing.net>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PKTGEN] fixing weird termio issues that complicate debugging
Date: Wed, 17 Feb 2016 12:13:00 +0200 [thread overview]
Message-ID: <56C447AC.4070309@redhat.com> (raw)
In-Reply-To: <FCB82F1C-A5ED-411A-AED5-F4D2CEF6D4AD@intel.com>
On 01/23/2016 04:22 AM, Wiles, Keith wrote:
> On 1/22/16, 1:45 AM, "Panu Matilainen" <pmatilai@redhat.com> wrote:
>> We wouldn't be discussing this if it was not an issue. It is offensive
>> enough to turn away both users and contributors, and merely speeding up
>> a bit is not going to make it a whole lot better.
>>
>> As I (and now others as well) already suggested changing it to a one
>> line printout is what would make worlds of difference while still
>> complying with the license AFAICT. The license text requires printing
>> out the copyright notice, it does not say anything about rendering it in
>> full-screen ascii-art, or printing out the entire license.
>
> Thank you Panu for your input, I will think about.
Looking at pktgen 2.9.12 and seeing all the ugly startup goo is now
gone, its my turn to
THANK YOU!
- Panu -
prev parent reply other threads:[~2016-02-17 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 6:32 Matthew Hall
2016-01-20 8:53 ` Panu Matilainen
2016-01-20 15:59 ` Wiles, Keith
2016-01-20 16:26 ` Wiles, Keith
2016-01-20 16:45 ` Wiles, Keith
2016-01-21 3:53 ` Matthew Hall
2016-01-21 8:46 ` Panu Matilainen
2016-01-21 15:03 ` Wiles, Keith
2016-01-21 19:00 ` Stephen Hemminger
2016-01-21 20:03 ` Matthew Hall
2016-01-22 6:45 ` Panu Matilainen
2016-01-23 2:22 ` Wiles, Keith
2016-02-17 10:13 ` Panu Matilainen [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=56C447AC.4070309@redhat.com \
--to=pmatilai@redhat.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=mhall@mhcomputing.net \
/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;
as well as URLs for NNTP newsgroup(s).