From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 1/2] metadata: add tests grouping support
Date: Thu, 18 Jun 2026 15:43:15 +0200 [thread overview]
Message-ID: <ajP187rd7nSV-Krv@yuki.lan> (raw)
In-Reply-To: <6a33f151.34ecd23a.148835.82ec@mx.google.com>
Hi!
> I was thinking that having `@group foo` is cleaner. When we start to have
> multiple groups it can be really to handle multiple groups: for instance,
> we might end up having one line over 80 chars in the description.
>
> @groups foo1 bar1 foo2 bar2 foo3 bar3 ..
>
> Instead, we might have
>
> @group foo1
> @group bar1
> @group foo2
> @group bar2
> @group foo3
> @group bar3
>
> These strings are short, but if we have long names it can be weird
> to read having all of them on a single line.
I wasn't saying that we should support only one @groups command, rather
than that we would do:
@groups foo1 foo2 foo3
@groups bar1 bar2 bar3
That would allow us to write reasonably short lines and limit the number
of lines to a reasonable number as well.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-06-18 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 13:54 [LTP] [PATCH 0/2] Support metadata groups Andrea Cervesato
2026-06-12 13:54 ` [LTP] [PATCH 1/2] metadata: add tests grouping support Andrea Cervesato
2026-06-12 19:10 ` [LTP] " linuxtestproject.agent
2026-06-17 14:46 ` [LTP] [PATCH 1/2] " Cyril Hrubis
2026-06-18 13:23 ` Andrea Cervesato via ltp
2026-06-18 13:43 ` Cyril Hrubis [this message]
2026-06-18 13:44 ` Andrea Cervesato via ltp
2026-06-12 13:54 ` [LTP] [PATCH 2/2] doc: conf.py: Show groups in test catalog Andrea Cervesato
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=ajP187rd7nSV-Krv@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.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.