From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] Replacing runltp-ng with kirk
Date: Mon, 11 Sep 2023 13:14:07 +0200 [thread overview]
Message-ID: <ZP72f0JFeMhkNo9n@yuki> (raw)
In-Reply-To: <8ebe4638-fda2-43f0-98d6-8d49b9b5a1b5@suse.com>
Hi!
> The idea, now, is to replace runltp-ng, since it's not maintained
> anymore, and replace it with kirk in the LTP official release.
Given that runltp-ng evolved into kirk I suppose that replacing it with
kirk in LTP is what we should do, especially since nobody is going to
invest into runltp-ng anymore.
I suppose that we should:
- put kirk to some more offical place
should it live under linux-test-project umbrela?
- replace the submodule
- add symlink from runltp-ng to kirk
Does everyone agree or should we do something different?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-11 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 9:47 [LTP] Replacing runltp-ng with kirk Andrea Cervesato via ltp
2023-09-11 11:14 ` Cyril Hrubis [this message]
2023-09-13 9:49 ` Andrea Cervesato via ltp
2023-09-15 8:50 ` 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=ZP72f0JFeMhkNo9n@yuki \
--to=chrubis@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