From: Lisa Marie Seelye <lisa@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Non-x86 arches: Is distcc-2.8-r2 stable?
Date: 11 Aug 2003 13:19:28 -0400 [thread overview]
Message-ID: <1060622367.1721.22.camel@lisa.thedoh.com> (raw)
In-Reply-To: <1060130502.15424.1.camel@lisa.thedoh.com>
[-- Attachment #1: Type: text/plain, Size: 532 bytes --]
On Tue, 2003-08-05 at 20:41, Lisa Marie Seelye wrote:
> Well guys? Anyone brave enough to use distcc-2.8-r2 on a non-x86 arch?
> I think its time to get those other arches up to date. Let me know if
> there are any problems or if I can bump them up!
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).
--
Regards,
-Lisa
<Vix ulla tam iniqua pax, quin bello vel aequissimo sit potior>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-11 17:16 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 [this message]
2003-08-11 18:56 ` Jason Wever
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=1060622367.1721.22.camel@lisa.thedoh.com \
--to=lisa@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