From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] Cleanup of tools/ directory
Date: Mon, 14 Nov 2016 15:05:04 +0100 [thread overview]
Message-ID: <20161114140504.GE25055@rei.lan> (raw)
Hi!
I've stumbled upon the tools/ directory and there is quite a lot of
broken code that is not really useful for anything.
The Makefile skips netpipe*, pounder21 and top-LTP directories. Apart
from automatic changes nobody touched the top-LTP and netpipe* code for
more than six years, so I would say that it's safe enough to remove
these. The pounder21 had some fixes that looks like somebody is using
that so I guess that we should keep it.
Then there are files that looks like they could be removed as well:
* STPfailure_report.pl - most likely no change since 2004, looks useless o me
* ltp_master, ltp_check, README, ltpoutput*
- remnants of some automated framework that used ltprun script that
used runalltests.sh script, I will remove these since there is no
reason to keep them now
In short has anybody anything agains removal of netpipe*, top-LTP,
STPfailure_report.pl, ltp_master, ltp_check, README, and ltpoutput* from
the tools/ directory?
--
Cyril Hrubis
chrubis@suse.cz
next reply other threads:[~2016-11-14 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 14:05 Cyril Hrubis [this message]
2016-11-21 9:10 ` [LTP] [RFC] Cleanup of tools/ directory Jan Stancek
2016-11-21 11:21 ` 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=20161114140504.GE25055@rei.lan \
--to=chrubis@suse.cz \
--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