From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 3/3] Add test for NFS directory listing regression
Date: Wed, 24 Nov 2021 11:27:00 +0100 [thread overview]
Message-ID: <YZ4TdGCTtUdY6zmT@pevik> (raw)
In-Reply-To: <53cbb0b6-0744-d6e8-3f7b-5991b17e915f@suse.cz>
> On 24. 11. 21 10:50, Petr Vorel wrote:
> > Hi Martin,
> >>> - echo "-n x Create x files and x directories, default is 5000"
> >>> + echo "-n x Create x files and x directories, default is $FILE_COUNT"
> >>> }
> >> If you run `nfs07.sh -hn 123`, your version will print that the default
> >> is 123.
> > Out of curiosity (as it's not anything important) not sure what's wrong on my
> > side (I tested it before I suggested it, I also reinstalled LTP to make sure
> > it's updated), but it works as expected:
> Ah, sorry, I've put the arguments in the wrong order.
> `nfs07.sh -n 123 -h` will overwrite $FILE_COUNT before printing usage info.
Ah, correct, thanks! I should have figured this out myself.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-11-24 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 15:15 [LTP] [PATCH v2 1/3] nfs_lib.sh: Add nfs_get_remote_path() Martin Doucha
2021-11-23 15:15 ` [LTP] [PATCH v2 2/3] nfs_lib.sh: Add support for test-specific parameters Martin Doucha
2021-11-23 19:29 ` Petr Vorel
2021-11-23 15:15 ` [LTP] [PATCH v2 3/3] Add test for NFS directory listing regression Martin Doucha
2021-11-23 19:40 ` Petr Vorel
2021-11-24 9:27 ` Martin Doucha
2021-11-24 9:50 ` Petr Vorel
2021-11-24 10:06 ` Martin Doucha
2021-11-24 10:27 ` Petr Vorel [this message]
2021-11-24 14:07 ` Alexey Kodanev
2021-11-24 14:12 ` Martin Doucha
2021-11-25 11:06 ` Petr Vorel
2021-11-25 13:27 ` Petr Vorel
2021-11-23 19:26 ` [LTP] [PATCH v2 1/3] nfs_lib.sh: Add nfs_get_remote_path() Petr Vorel
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=YZ4TdGCTtUdY6zmT@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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