From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 2/2] include/old: rename legacy headers to tso_* namespace
Date: Thu, 29 Jan 2026 00:26:16 +0100 [thread overview]
Message-ID: <20260128232616.GA69843@pevik> (raw)
In-Reply-To: <CAEemH2fkn3C4ov0YL9sx5SiBMuWEOoNfrwAzEsOwCZZDTtuEwA@mail.gmail.com>
Hi Li, all,
> > As I wrote, I don't like the whole rename but I will not block it.
> > I guess it will be merged after the release, just not to break anything.
> > But is it worth to rename whole old API sources and headers? Isn't it
> > enough
> > just to know that 'tst_' or 'tse_' are new API, the rest is the old API or
> > no
> > API? Each rename means that 'git log' requires '--' because the rename.
> Well, yes, that's my hesitation too.
> However, I believe the old APIs may persist for a long time. Therefore,
> using consistent naming conventions for all APIs will make it easier for
> LTP beginners to understand the code logic.
OK. Ack for both commits.
Acked-by: Petr Vorel <pvorel@suse.cz>
> > Anyway, IMHO it would help (as a separate effort after the release) to
> > describe
> > the prefixes in doc.
> Yes, it's not a rush, we could give enough time for refinement work.
+1
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-01-28 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 2:25 [LTP] [PATCH v2 1/2] libs: adopt tse_ prefix for extended (non-core) library Li Wang via ltp
2026-01-16 2:25 ` [LTP] [PATCH v2 2/2] include/old: rename legacy headers to tso_* namespace Li Wang via ltp
2026-01-16 9:04 ` Li Wang via ltp
2026-01-28 21:22 ` Petr Vorel
2026-01-28 23:20 ` Li Wang via ltp
2026-01-28 23:26 ` Petr Vorel [this message]
2026-02-01 23:52 ` Li Wang via ltp
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=20260128232616.GA69843@pevik \
--to=pvorel@suse.cz \
--cc=liwang@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 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.