From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3 3/3] app/testpmd: improve output when processing cmdline files
Date: Mon, 28 Jul 2025 21:24:22 -0700 [thread overview]
Message-ID: <20250728212422.2c86915c@hermes.local> (raw)
In-Reply-To: <20250707111751.183469-4-bruce.richardson@intel.com>
On Mon, 7 Jul 2025 12:17:51 +0100
Bruce Richardson <bruce.richardson@intel.com> wrote:
> Two small improvements for the cmdline file processing in testpmd.
>
> * Now that we support multiple files, change the prompt to indicate what
> file is currently being processed, and just print an EOF message when
> done.
> * When not echoing, the "Read" verb in the message "Read CLI commands..."
> is a little ambiguous, as it could mean "I have read", or "Go and read",
> i.e. job done or job about to start. Tweak the text to "Finished reading"
> which is unambiguous.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
>
> Owing to limitations of whats available on windows, e.g. no basename
> function, the windows implementation prints N characters from the end of
> the filename, if its too long. While I don't think this is as good as the
> basename version used on Linux/Unix, if we want to have common code, we can
> just use that as a common version everywhere and drop the basename version.
I would prefer just having basename() wrapper like other helpers
we have already for Windows. Get from FreeBSD or other BSD licensed source
(or write your own).
Having two #ifdefs creates needless platform difference here.
prev parent reply other threads:[~2025-07-29 4:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 14:05 [PATCH] app/testpmd: allow multiple cmdline-file parameters Bruce Richardson
2025-07-04 18:34 ` [PATCH v2 0/3] improve cmdline file handling in testpmd Bruce Richardson
2025-07-04 18:34 ` [PATCH v2 1/3] app/testpmd: explicitly set command echoing on file load Bruce Richardson
2025-07-04 18:34 ` [PATCH v2 2/3] app/testpmd: allow multiple commandline file parameters Bruce Richardson
2025-07-04 18:34 ` [PATCH v2 3/3] app/testpmd: improve output when processing cmdline files Bruce Richardson
2025-07-07 11:17 ` [PATCH v3 0/3] improve cmdline file handling in testpmd Bruce Richardson
2025-07-07 11:17 ` [PATCH v3 1/3] app/testpmd: explicitly set command echoing on file load Bruce Richardson
2025-07-07 11:17 ` [PATCH v3 2/3] app/testpmd: allow multiple commandline file parameters Bruce Richardson
2025-07-07 11:17 ` [PATCH v3 3/3] app/testpmd: improve output when processing cmdline files Bruce Richardson
2025-07-29 4:24 ` Stephen Hemminger [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=20250728212422.2c86915c@hermes.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@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).