From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 0/2] Cleanup runtests containing duplicate definitions
Date: Mon, 5 Nov 2018 10:05:02 -0500 (EST) [thread overview]
Message-ID: <863155656.69419841.1541430302026.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAEemH2fxHBmWmuj314ZdB+E2i2wXBtOg40SrSgt2Vxtqcns=0Q@mail.gmail.com>
----- Original Message -----
> Jan, did we internal ltp-lite take reference from the ltplite file?
Probably only at the beginning, when original author of beaker test
forked ltplite runtest file. I've been using syscalls/other runtest
files, since those are more up to date.
> I wanna
> know how do we customize our internal ltp-lite testcases.
syscalls + cherry-picked tests from other runtest files.
We might be getting off-topic w.r.t this mailing list.
Regards,
Jan
>
> -- Sending by my PH1 phone.
>
> On Mon, Nov 5, 2018, 19:43 Petr Vorel <pvorel@suse.cz wrote:
>
> > Hi,
> >
> > > anyone using these? Objections?
> > > IMHO there is no point trying to keep them sync.
> > It looks like no objection to this, so I'll remove it.
> >
> > Kind regards,
> > Petr
> >
>
next prev parent reply other threads:[~2018-11-05 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 20:18 [LTP] [RFC PATCH 0/2] Cleanup runtests containing duplicate definitions Petr Vorel
2018-10-15 20:18 ` [LTP] [RFC PATCH 1/2] Remove LTP stress tests Petr Vorel
2018-10-15 20:18 ` [LTP] [RFC PATCH 2/2] Remove ltplite and runltplite.sh Petr Vorel
2018-11-05 11:43 ` [LTP] [RFC PATCH 0/2] Cleanup runtests containing duplicate definitions Petr Vorel
2018-11-05 14:34 ` Li Wang
2018-11-05 15:05 ` Jan Stancek [this message]
2018-11-05 19:01 ` Petr Vorel
2018-11-06 9:25 ` Li Wang
2018-11-06 9:43 ` 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=863155656.69419841.1541430302026.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.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