From: Richard Palethorpe <rpalethorpe@suse.de>
To: rpalethorpe@suse.de
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Add runltp-ng to upstream
Date: Mon, 12 Dec 2022 15:06:51 +0000 [thread overview]
Message-ID: <875yegu090.fsf@suse.de> (raw)
In-Reply-To: <87h6yauu9v.fsf@suse.de>
Hello,
Richard Palethorpe <rpalethorpe@suse.de> writes:
> Hello,
>
> Andrea Cervesato via ltp <ltp@lists.linux.it> writes:
>
>> runltp-ng is the next generation runner for Linux Testing Project and it
>> will replace the current obsolete runltp script in the next future.
>>
>> 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..e85fc6279 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 = https://github.com/acerv/runltp-ng
>
> NACK
>
> We should move the project into the linux-test-project org first.
I am in favor of doing this, but set to "changes requested" in
patchwork.
>
>> diff --git a/tools/runltp-ng b/tools/runltp-ng
>> new file mode 160000
>> index 000000000..b08471158
>> --- /dev/null
>> +++ b/tools/runltp-ng
>> @@ -0,0 +1 @@
>> +Subproject commit b0847115891bd3dddbe920a716342917e7088379
>> --
>> 2.35.3
>
>
> --
> Thank you,
> Richard.
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-12-12 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 10:30 [LTP] [PATCH v1] Add runltp-ng to upstream Andrea Cervesato via ltp
2022-12-02 14:01 ` Petr Vorel
2022-12-05 8:23 ` Andrea Cervesato via ltp
2022-12-05 11:03 ` Petr Vorel
2022-12-05 8:29 ` Richard Palethorpe
2022-12-12 15:06 ` Richard Palethorpe [this message]
2022-12-20 12:27 ` Cyril Hrubis
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=875yegu090.fsf@suse.de \
--to=rpalethorpe@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.