public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan Coutts <duncan.coutts@worc.ox.ac.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keywording, for the umpteenth time
Date: Fri, 20 May 2005 19:53:09 +0100	[thread overview]
Message-ID: <1116615190.8364.203.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.63.0505201034300.4132@stargazer.weeve.org>

On Fri, 2005-05-20 at 10:42 -0600, Jason Wever wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> OK, let's review this again.
> 
> If you cannot test a given ebuild on a given arch, then don't touch that 
> arch's keyword (unless you need to remove it for broken dependencies).
> 
> If you can test for a given arch and are not part of that arch team, 
> please please please let the arch teams know that before you go around 
> keywording things arbitrarily.  It makes the baby Jesus cry when you don't 
> and really isn't the greatest from a QA perspective either.

Sorry folks this was my fault. I've sent my grovelling apology to the
sparc team. Hopefully they'll accept my apologies and put my digressions
down to me being a new dev. :-)

Actually I did do fairly thorough testing / QA but I didn't tell the
arch team before keywording (bad me!).

In case anyone is interested; this is about the Haskell packages which I
hope to get up to scratch on sparc (with the consent and approval of the
sparc team in future!)

Duncan

-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-05-20 18:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 16:42 [gentoo-dev] Keywording, for the umpteenth time Jason Wever
2005-05-20 18:53 ` Duncan Coutts [this message]
2005-05-20 19:42   ` Mike Frysinger
2005-05-20 20:09   ` Jason Wever
2005-05-20 20:51     ` Brian Jackson
2005-05-20 21:18       ` Michael Cummings
2005-05-21  0:17         ` Donnie Berkholz
2005-05-20 21:22       ` Ciaran McCreesh
2005-05-20 21:49         ` Tom Wesley
2005-05-20 22:38           ` Ciaran McCreesh

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=1116615190.8364.203.camel@localhost \
    --to=duncan.coutts@worc.ox.ac.uk \
    --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