From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Li Wang" <liwang@redhat.com>, "Jan Stancek" <jstancek@redhat.com>
Cc: Pradeep Susarla <pradeep.susarla@gmail.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] libs: adopt lib* prefix instead of tst_* for libs/
Date: Wed, 14 Jan 2026 14:36:31 +0100 [thread overview]
Message-ID: <DFOCP67N3URJ.1JRGHBYX4VFJF@suse.com> (raw)
In-Reply-To: <CAEemH2c_HQ1pb0-HF_gMJHsQFde50pjmZ+au120zdhQt7x=rFA@mail.gmail.com>
On Wed Jan 14, 2026 at 1:47 PM CET, Li Wang wrote:
> > > Perhaps we can use a lightweight name for the extra libs/:
> > >
> > > est_*: extra test library
> > > xst_*: extened test library
> > > lst_*: ltp test library
> > >
> >
> > Otherwise we can have `tst_` tag for all libraries inside LTP, but
> > divide them into categories according to their meaning:
> >
> > - tst_*: test library
> > - tst_lib_*: libraries inside LTP
> > - tst_old_*: old test libraries
>
> It might not be good (too long) to use tst_lib_ in the function names,
> which not easy to distinguish from tst_.
>
> To combine with ltpx_ suggestion, I guess we could use:
>
> tst_*: core test library
> etst_*: non-core (extended) test library
> otst_*: old test library
>
> The reason I'm not using the word "ltp" is that it's too broad,
> we're better off naming it around *tst*.
I guess we reached a point where 5 engineers found 7 different
solutions. For me it's all good as long as we keep the "tst" tag to make
sure we know we are importing LTP stuff :-)
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-01-14 13:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 2:39 [LTP] [PATCH] libs: adopt lib* prefix instead of tst_* for libs/ Li Wang via ltp
2026-01-09 3:07 ` Li Wang via ltp
2026-01-12 12:59 ` Andrea Cervesato via ltp
2026-01-12 14:10 ` Li Wang via ltp
2026-01-13 11:51 ` Petr Vorel
2026-01-13 13:30 ` Jan Stancek via ltp
2026-01-13 13:41 ` Andrea Cervesato via ltp
2026-01-14 3:03 ` Li Wang via ltp
2026-01-14 8:51 ` Petr Vorel
2026-01-14 10:32 ` Li Wang via ltp
2026-01-14 11:33 ` Petr Vorel
2026-01-14 11:58 ` Li Wang via ltp
2026-01-14 12:18 ` Jan Stancek via ltp
2026-01-14 12:07 ` Andrea Cervesato via ltp
2026-01-14 12:47 ` Li Wang via ltp
2026-01-14 13:36 ` Andrea Cervesato via ltp [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=DFOCP67N3URJ.1JRGHBYX4VFJF@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=jstancek@redhat.com \
--cc=liwang@redhat.com \
--cc=pradeep.susarla@gmail.com \
/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