On Wed, Jan 9, 2013 at 12:02 PM, Jeroen Roovers wrote:
> A lot clearer than a single text field littered with keywords would be some
> tick boxes, indeed. In fact, it makes me wonder why we use a half-obscured
> list
> in a select field for adding/removing arch teams now.
Agree - mostly legacy (
On Wed, 9 Jan 2013 18:39:09 +0200
Markos Chandras wrote:
> On 9 January 2013 18:17, Vicente Olivert Riera
> > some devs and I were talking about the fact that TESTED bugzilla
> > keyword may need a change on his description, or, maybe it's needed
> > to create new TESTED_${ARCH} keywords.
> >
>
On 9 January 2013 18:17, Vicente Olivert Riera wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello everyone :-)
>
> some devs and I were talking about the fact that TESTED bugzilla
> keyword may need a change on his description, or, maybe it's needed to
> create new TESTED_${ARCH} k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everyone :-)
some devs and I were talking about the fact that TESTED bugzilla
keyword may need a change on his description, or, maybe it's needed to
create new TESTED_${ARCH} keywords.
Personally, I was using TESTED keyword when an ebuild was t
