From: Ionen Wolkens <sudinave@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Continuous integration on GURU
Date: Thu, 22 Apr 2021 08:59:00 -0400 [thread overview]
Message-ID: <YIFzFF9i51doxsum@eversor> (raw)
In-Reply-To: <2113586.72vocr9iq0@spectre>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
On Thu, Apr 22, 2021 at 02:39:02PM +0200, Agostino Sarubbo wrote:
> On giovedì 22 aprile 2021 12:02:20 CEST Michał Górny wrote:
> > One more thing: might be a good idea to consider splitting some
> > of the 'big' trackers (like CFLAGS) between Gentoo and GURU. I think
> > solving these bugs in GURU has lower priority than in Gentoo.
>
> I think that trackers like CFLAGS/LDFLAGS are here to track how many packages
> have the problem. I don't see it like (for example) the gcc-porting tracker
> that gives the idea about how much packages need a fix and how much packages
> need to be last-rited
If want to track, can't we just have separate tracker(s) for GURU?
Now when look at this tracker can't tell how much is ::gentoo or
::guru without doing some extra work.
And, even if you don't see it like that, someday someone may want
to go on a fixing spree using those trackers (may it be for ::guru
or ::gentoo) but will keep seeing them mixed up together.
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-04-22 12:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 9:59 [gentoo-dev] Continuous integration on GURU Agostino Sarubbo
2021-04-22 10:02 ` Michał Górny
2021-04-22 12:39 ` Agostino Sarubbo
2021-04-22 12:59 ` Ionen Wolkens [this message]
2021-04-22 13:11 ` Agostino Sarubbo
2021-04-22 13:23 ` Sam James
2021-04-22 13:31 ` Agostino Sarubbo
2021-04-22 13:57 ` Sam James
2021-04-22 13:01 ` Wolfgang E. Sanyer
2021-04-22 13:03 ` Michał Górny
2021-04-22 13:10 ` Andrew Ammerlaan
2021-04-22 10:22 ` Theo Anderson
2021-04-22 11:30 ` Agostino Sarubbo
2021-04-22 13:45 ` Theo Anderson
2021-04-22 13:59 ` Ionen Wolkens
2021-04-22 17:58 ` Agostino Sarubbo
2021-04-22 10:25 ` Michał Górny
2021-04-22 11:27 ` Agostino Sarubbo
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=YIFzFF9i51doxsum@eversor \
--to=sudinave@gmail.com \
--cc=gentoo-dev@lists.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