From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] Add runltp-ng to upstream
Date: Tue, 20 Dec 2022 15:22:38 +0100 [thread overview]
Message-ID: <Y6HFLu3vkOJVMBwn@pevik> (raw)
In-Reply-To: <20221220124351.5001-1-andrea.cervesato@suse.com>
Hi all,
> runltp-ng is the next generation runner for Linux Testing Project and it
> will replace the current obsolete runltp script in the next future.
changes v1->v2
* repository moved to LTP github namespace
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> .gitmodules | 3 +++
> tools/runltp-ng | 1 +
> 2 files changed, 4 insertions(+)
> create mode 160000 tools/runltp-ng
> diff --git a/.gitmodules b/.gitmodules
> index a3c34af4b..810eac395 100644
> --- a/.gitmodules
> +++ b/.gitmodules
> @@ -4,3 +4,6 @@
> [submodule "tools/sparse/sparse-src"]
> path = tools/sparse/sparse-src
> url = git://git.kernel.org/pub/scm/devel/sparse/sparse.git
> +[submodule "tools/runltp-ng"]
> + path = tools/runltp-ng
> + url = git@github.com:linux-test-project/runltp-ng.git
Wouldn't be better to use https ?
- url = git@github.com:linux-test-project/runltp-ng.git
+ url = https://github.com/linux-test-project/runltp-ng.git
Or are there problems with certificates? If agree on https,
we of course should migrate other
Otherwise LGTM
Acked-by: Petr Vorel <pvorel@suse.cz>
Kind regards,
Petr
> diff --git a/tools/runltp-ng b/tools/runltp-ng
> new file mode 160000
> index 000000000..af20a864e
> --- /dev/null
> +++ b/tools/runltp-ng
> @@ -0,0 +1 @@
> +Subproject commit af20a864ec01674ce4f5a21d3308dc3a76da9303
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-12-20 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 12:43 [LTP] [PATCH v2] Add runltp-ng to upstream Andrea Cervesato via ltp
2022-12-20 14:10 ` Richard Palethorpe
2022-12-20 14:22 ` Petr Vorel [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=Y6HFLu3vkOJVMBwn@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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