public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Wever <weeve@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Non-x86 arches: Is distcc-2.8-r2 stable?
Date: Mon, 11 Aug 2003 14:56:49 -0400	[thread overview]
Message-ID: <20030811145649.708cbdee.weeve@gentoo.org> (raw)
In-Reply-To: <1060622367.1721.22.camel@lisa.thedoh.com>

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

On 11 Aug 2003 13:19:28 -0400
Lisa Marie Seelye <lisa@gentoo.org> wrote:

> Well since I haven't heard anything from the non-x86 people I'm going to
> bump 2.8-r2 to stable on those arches and 2.9 to x86 (I'll post a formal
> announcement after I get 2.10 in).

(Note: this is in general as well as specifically to this instance).

PLEASE PLEASE PLEASE DO NOT MAKE THIS DEFAULT BEHAVIOR.

Right now most non-x86 arches have a small number of devs and a small
amount of time in which to test.  

I would like to request (was going to GLEP it when time permits) that if
you want to test something for an arch you can't test, please make a bug
for it.  This way it's sure to get visibility and you actually know that
an arch person tested it.  Mailing lists are a poor way to ask for testing
and the testing requests are easily lost in the myraids of email that a
dev has to read when they get home from work/school/whatever each day.

Thanks,
-- 
Jason Wever
Gentoo/Sparc Team Lead

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-11 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06  0:41 [gentoo-dev] Non-x86 arches: Is distcc-2.8-r2 stable? Lisa Marie Seelye
2003-08-11 17:19 ` Lisa Marie Seelye
2003-08-11 18:56   ` Jason Wever [this message]
2003-08-11 19:12   ` Michael Cummings
2003-08-11 23:40     ` Lisa Marie Seelye
2003-08-11 23:58       ` Kumba

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=20030811145649.708cbdee.weeve@gentoo.org \
    --to=weeve@gentoo.org \
    --cc=gentoo-dev@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