From: Weeve <weeve@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Testing required for stable bumps
Date: Fri, 25 Jul 2003 07:38:33 -0400 [thread overview]
Message-ID: <20030725073833.141e5f0d.weeve@gentoo.org> (raw)
In-Reply-To: <200307251108.44661.lanius@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
On Fri, 25 Jul 2003 11:08:44 +0200
Heinrich Wendel <lanius@gentoo.org> wrote:
> Hi,
>
> I want to mark the following packages stable, but they still need testing on
> non-x86 arches:
>
(snip)
> cups-1.1.19-r1
Can we hold off on stabilizing this until bug #24759 is resolved? I don't believe it impairs functionality (other than keeping a good eye on startup scripts at boot time) but cups never used to do this.
Thanks,
--
Weeve
Gentoo/Sparc Team Lead
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-25 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 9:08 [gentoo-dev] Testing required for stable bumps Heinrich Wendel
2003-07-25 11:38 ` Weeve [this message]
2003-07-25 11:48 ` Heinrich Wendel
2003-07-25 12:07 ` Weeve
2003-07-25 16:02 ` Brian Jackson
2003-07-27 15:39 ` Ferris McCormick
2003-07-28 15:29 ` [gentoo-dev] Testing required for stable bumps (tetex-2.0.2) Ferris McCormick
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=20030725073833.141e5f0d.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