From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] libs: Remove 'libltp' prefix from libs source directories
Date: Mon, 24 Jun 2024 14:31:24 +0200 [thread overview]
Message-ID: <ZnlnHOGlHDOyhImb@yuki> (raw)
In-Reply-To: <CAEemH2eZNO=P5c_igqNKSva-q37y7GSK=d44wUHd=Ua=DTUNDw@mail.gmail.com>
Hi!
> > I know renaming files is not optimal. But history will be kept, when
> > browsing with gitk or git gui.
> >
> > Improvement: less typing when cd to the directory.
> >
I do not have a strong opinion on this, feel free to push the change
with my:
Acked-by: Cyril Hrubis <chrubis@suse.cz>
> +1 I agree with this, and I always have a question, why
> we have additional libs/ parallel with lib/, is there any root
> difference between them? or just a historical issue?
The idea is exactly how it was described by Peter, these are usually
libraries used only by a few tests e.g. functions to deal with swap or
linux input, while lib/ has functions that are used by most of
the tests with more generic functionalities.
Apart from small speedup it makes things a bit easier to navigate, at
least I think so. Or do you think that this would be better with all the
files in a single directory?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-06-24 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 11:02 [LTP] [PATCH 1/1] libs: Remove 'libltp' prefix from libs source directories Petr Vorel
2024-04-20 1:41 ` Li Wang
2024-04-20 8:54 ` Petr Vorel
2024-06-24 12:31 ` Cyril Hrubis [this message]
2024-06-24 12:52 ` Li Wang
2024-07-29 8:27 ` 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=ZnlnHOGlHDOyhImb@yuki \
--to=chrubis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox