From: Brad Laue <brad@brad-x.com>
To: danarmak@gentoo.org
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuilds not getting in :(
Date: Fri, 25 Apr 2003 12:58:20 -0400 [thread overview]
Message-ID: <3EA9692C.4040109@brad-x.com> (raw)
In-Reply-To: <200304221726.35741.danarmak@gentoo.org>
Dan Armak wrote:
> Just a quick note (without addressing your main point). ~arch is _not_
> "unstable". It is not supposed to be unstable in the literal meaning of the
> word. It is 'testing', or 'works for me'. Developers can _not_ commit things,
> or leave things, unmasked in ~x86 that have known issues, or that are
> alpha-quality releases from upstream. (This doesn't apply directly to what
> you were saying, I just don't like to see it called unstable...)
Okay, it seems to me that squid 2.5 and apache 2.0 don't belong in the
~x86 keyword then; I had considered this okay under the mistaken
impression that this was an 'unstable' rather than a testing branch.
Apache and squid's devel versions should be slotted, masked or placed in
their own ebuilds, by the sounds of what you're saying. Agreed?
Brad
--
// -- http://www.BRAD-X.com/ -- //
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-25 16:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 7:38 [gentoo-dev] Ebuilds not getting in :( Klavs Klavsen
2003-04-22 12:59 ` Frantz Dhin
2003-04-22 13:09 ` Ragnar Hojland Espinosa
2003-04-22 13:17 ` Peter Ruskin
2003-04-22 13:24 ` FRLinux
2003-04-22 13:30 ` Klavs Klavsen
2003-04-22 13:50 ` Ragnar Hojland Espinosa
2003-04-22 14:05 ` Jon Portnoy
2003-04-22 16:18 ` Brad Laue
2003-04-23 15:25 ` Peter Ruskin
2003-04-23 18:18 ` Paul de Vrieze
2003-04-22 14:26 ` Dan Armak
2003-04-22 14:57 ` Peter Ruskin
2003-04-22 15:40 ` Tony Clark
2003-04-22 15:45 ` Ragnar Hojland Espinosa
2003-04-22 16:00 ` Klavs Klavsen
2003-04-22 16:14 ` Tony Clark
2003-04-22 16:23 ` William Hubbs
2003-04-22 16:59 ` Jon Portnoy
2003-04-22 17:55 ` Mark Bainter
2003-04-22 18:00 ` Klavs Klavsen
2003-04-22 18:06 ` Jon Portnoy
2003-04-25 16:58 ` Brad Laue [this message]
2003-04-25 17:31 ` foser
2003-04-25 21:03 ` Brad Laue
2003-04-26 0:38 ` foser
2003-04-22 19:11 ` Fredrik Jagenheim
2003-04-22 23:53 ` Fernand Albarracin
2003-04-22 15:57 ` Brian Jackson
2003-04-22 22:07 ` Brian Jackson
2003-04-22 22:36 ` Robin H.Johnson
2003-04-23 7:43 ` Mark Gordon
2003-04-23 12:46 ` Jon Portnoy
[not found] ` <20030425134659.I30851@leftmind.net>
2003-04-25 21:59 ` Robin H.Johnson
2003-04-23 2:56 ` Brian Jackson
2003-04-23 15:27 ` Peter Fein
2003-04-23 15:38 ` Grant Goodyear
2003-04-24 18:20 ` Brian Jackson
2003-04-23 5:47 ` Thomas Arnhold
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 0:32 Stroller
2003-04-24 3:50 ` George Shapovalov
2003-04-25 1:01 Stroller
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=3EA9692C.4040109@brad-x.com \
--to=brad@brad-x.com \
--cc=danarmak@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