public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Suggestion related with dropping keywords policy
Date: Thu, 17 Jun 2010 14:04:42 +0200	[thread overview]
Message-ID: <1276776282.22475.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20100617060715.4e0163a1@epia.jer-c2.orkz.net>

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

El jue, 17-06-2010 a las 06:07 +0200, Jeroen Roovers escribió:
> On Fri, 11 Jun 2010 07:39:01 -0400
> Joseph Jezak <josejx@gentoo.org> wrote:
> 
> > Your preferred method is exactly how (as a ppc keyworder) I like to
> > see these kind of bugs handled. Dropping keywords makes an awful lot
> > more work for us and hurts our users, especially since we're not
> > always very prompt at handling bugs.
> 
> Well, reasoning for the HPPA team, which maintains an architecture
> that is dying rather more quickly than PPC32 (which still has all kinds
> of embedded uses and so on),, in favour of IA64, I'd rather see dropped
> keywords than new profile entries, possibly with the keyworded ebuilds
> being gradually removed after an OK. That way I can make a choice to
> keep a package (set) for a bit or to stop supporting it immediately.
> 

In that case, could you then consider to un-CC from keywording bugs hppa
team is not willing to fix? I think it would help a lot to "clean" the
tree of old versions that are been kept as it's the inly keyworded on
hppa

Thanks a lot

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-06-17 12:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11  9:27 [gentoo-dev] Suggestion related with dropping keywords policy Pacho Ramos
2010-06-11  9:39 ` Thilo Bangert
2010-06-11 11:39 ` Joseph Jezak
2010-06-17  4:07   ` Jeroen Roovers
2010-06-17 12:04     ` Pacho Ramos [this message]
2010-06-17 17:41       ` Jeroen Roovers
2010-06-13 11:16 ` Petteri Räty
2010-06-13 12:43   ` Pacho Ramos
2010-06-13 22:29     ` Pacho Ramos
2010-06-14  2:59       ` Jeroen Roovers
2010-06-14  8:08         ` Pacho Ramos
2010-06-14  9:30           ` Jeroen Roovers
2010-06-14  9:44             ` Pacho Ramos
2010-06-14  8:21         ` Petteri Räty

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=1276776282.22475.4.camel@localhost.localdomain \
    --to=pacho@gentoo.org \
    --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