public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wesley <tom@tomaw.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keywording, for the umpteenth time
Date: Fri, 20 May 2005 22:49:50 +0100	[thread overview]
Message-ID: <1116625790.9174.5.camel@tom.tomaw.org> (raw)
In-Reply-To: <20050520222238.157d8270@snowdrop>

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

On Fri, 2005-05-20 at 22:22 +0100, Ciaran McCreesh wrote:
> Not gonna happen. Emulators don't cut it and won't find all the problems
> (but they will find a load of other bogus non-issues). Plus, from
> experience I'd say that at least half our devs wouldn't have a clue
> where to start when doing arch testing...

Add this HOWTO arch test to your developer docs.  Very nice by the way.

> Then there's the issue of most alt-archs having far higher QA standards
> than x86 anyway, and us not wanting to sink to what x86 considers
> acceptable for marking stable.
> 
> From experience -- the current policy as it is now *works*, so long as
> everyone follows it.

And as long as ciaranm, or someone from a non x86 arch bitches once a
month here.

-- 
Tom Wesley <tom@tomaw.org>

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

  reply	other threads:[~2005-05-20 21:52 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
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 [this message]
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=1116625790.9174.5.camel@tom.tomaw.org \
    --to=tom@tomaw.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