From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "spp@dpdk.org" <spp@dpdk.org>
Subject: Re: [spp] [PATCH 2/2] spp_vf: update to improve usability
Date: Wed, 28 Feb 2018 19:27:11 +0900 [thread overview]
Message-ID: <e3ccced1-0ed5-db76-cde3-40423958cbff@lab.ntt.co.jp> (raw)
In-Reply-To: <79cbf414-ecef-8793-b688-d16d9d3cb15a@intel.com>
On 2018/02/22 20:50, Ferruh Yigit wrote:
> On 2/8/2018 3:18 PM, ogawa.yasufumi@lab.ntt.co.jp (ogawa.yasufumi@lab.ntt.co.jp)
> wrote:
>> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>>
>> This update is same as previous patch for spp.py.
>>
>> * Override emptyline() of Shell class to not repeat previous command.
>>
>> * Override default() to accept comment line. To find the comment, add
>> is_comment_line() which support python and C style comment.
>>
>> * Remove lower() for user's input to avoid unexpected behaviour.
>>
>> Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>
> Hi Yasufumi,
>
> This is already applied but I am concerned about having two version of python
> script, spp.py and spp_vf.py.
>
> Is there a long term plan for them?
> Why we are maintaining two copies and they are slightly differentiated now, as
> some features only supported in spp_vf.py?
Ferruh,
I think I should move spp_vf features to spp.py. We started to develop
spp_vf as an experimental project independently, but it is merged SPP repo.
As you mentioned, spp_vf.py has features only for spp_vf, however I
think it can be moved to spp.py as an extension or plugin to not lose
usability. I'd like to consider it.
Thanks,
Yasufumi
>
> Does it make sense to merge them?
>
> Thanks,
> ferruh
>
>
--
Yasufumi Ogawa
NTT Network Service Systems Labs
next prev parent reply other threads:[~2018-02-28 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 15:18 [spp] [PATCH 1/2] spp: " ogawa.yasufumi
2018-02-08 15:18 ` [spp] [PATCH 2/2] spp_vf: " ogawa.yasufumi
2018-02-22 11:50 ` Ferruh Yigit
2018-02-28 10:27 ` Yasufumi Ogawa [this message]
2018-02-22 11:35 ` [spp] [PATCH 1/2] spp: " Ferruh Yigit
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=e3ccced1-0ed5-db76-cde3-40423958cbff@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.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;
as well as URLs for NNTP newsgroup(s).