public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Dummer <martin.dummer@gmx.net>
To: gentoo-dev@lists.gentoo.org, Sam James <sam@gentoo.org>,
	Eli Schwartz <eschwartz93@gmail.com>
Subject: Re: [gentoo-dev] [PATCH] vdr-plugin-2.eclass: make qa warning conditional
Date: Thu, 9 May 2024 14:08:03 +0200	[thread overview]
Message-ID: <5803c021-601d-48b2-bbfa-ce5de555e1cf@gmx.net> (raw)
In-Reply-To: <87cyq3ldah.fsf@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]


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.

Maybe we can agree that the qa-warnings in vdr-eclass make more sense if
i change them to "eawarn" or "einfo"?

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.

[-- Attachment #2: Type: text/html, Size: 1945 bytes --]

  reply	other threads:[~2024-05-09 12:08 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 [this message]
2024-05-09 12:13       ` Sam James
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=5803c021-601d-48b2-bbfa-ce5de555e1cf@gmx.net \
    --to=martin.dummer@gmx.net \
    --cc=eschwartz93@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=sam@gentoo.org \
    /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