From: Sam James <sam@gentoo.org>
To: Martin Dummer <martin.dummer@gmx.net>
Cc: gentoo-dev@lists.gentoo.org, Eli Schwartz <eschwartz93@gmail.com>
Subject: Re: [gentoo-dev] [PATCH] vdr-plugin-2.eclass: make qa warning conditional
Date: Thu, 09 May 2024 13:13:02 +0100 [thread overview]
Message-ID: <87le4ji3ox.fsf@gentoo.org> (raw)
In-Reply-To: <5803c021-601d-48b2-bbfa-ce5de555e1cf@gmx.net> (Martin Dummer's message of "Thu, 9 May 2024 14:08:03 +0200")
Martin Dummer <martin.dummer@gmx.net> writes:
> Am 03.05.24 um 06:39 schrieb Sam James:
>
>
> What we really need is:
> a) https://bugs.gentoo.org/162450 to avoid scaring users;
> b) possibly some level of QA notice to distinguish between "check this
> out" (think e.g. qa-vdb LHS where it _might_ be unused, but not
> necessarily), and "this is definitely wrong"
>
> I am convinced we need a), I am not-at-all convinced we need b) - at
> least not in terms of whether bugs are reported.
>
> AFAIS https://bugs.gentoo.org/162450 is not implemented.
Right, that's why I didn't say "we can just use".
>
> Maybe we can agree that the qa-warnings in vdr-eclass make more sense if i change them to "eawarn" or "einfo"?
>
Sure, make them eqawarn.
> In my opinion, most plugins in the vdr context will practically not develop any further anyway. It is more important to
> keep the current status of vdr-software in the ecosystem up to date as well as possible.
>
> So I need a practical useful approach instead of a fundamental discussion please.
My point is that the QA warnings should exist, and you can worry about
making them "developer-only" in future. Right now, they seem useful, and
the things they flag need to be addressed.
next prev parent reply other threads:[~2024-05-09 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 14:10 [gentoo-dev] [PATCH] vdr-plugin-2.eclass: make qa warning conditional Martin Dummer
2024-05-01 15:07 ` Eli Schwartz
2024-05-03 4:39 ` Sam James
2024-05-09 12:08 ` Martin Dummer
2024-05-09 12:13 ` Sam James [this message]
2024-05-09 13:02 ` Martin Dummer
2024-05-09 13:08 ` Sam James
2024-05-10 15:42 ` Martin Dummer
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=87le4ji3ox.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=eschwartz93@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=martin.dummer@gmx.net \
/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