public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Kohl <citizen428@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Summary] tentative x86 arch team glep
Date: Mon, 12 Sep 2005 19:19:36 +0200	[thread overview]
Message-ID: <20050912191936.73ca6a75@localhost> (raw)
In-Reply-To: <4325B534.9010803@wildgooses.com>

On Mon, 12 Sep 2005 18:04:52 +0100
Ed W <lists@wildgooses.com> wrote:

> At the  simplest this could be used to allow a non core developer to
> bump an ebuild to a new version in response to some release.  It goes
> into the "highly unstable" section which shouldn't be seen by any
> normal person, yet at the same time makes it available to the kiddies
> who like to test the latest and greatest.

Isn't this what Break My Gentoo already provides?

http://www.breakmygentoo.net/

Personally I don't want to have to mess around with bugs for the
"highly unstable" section you mentioned, and I have a feeling that a
quite a lot of people share this sentiment. 

-- 
web@citizen428.net                                 citizen428@gentoo.org
http://citizen428.net/                http://dev.gentoo.org/~citizen428/
GnuPG key: 0x90CA09E3/4D21 916E DBCE 72B8 CDC5  BD87 DE2D 91A2 90CA 09E3
-- 
gentoo-dev@gentoo.org mailing list



      reply	other threads:[~2005-09-12 17:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 10:03 [gentoo-dev] [Summary] tentative x86 arch team glep Chris White
2005-09-06 12:35 ` Mike Doty
2005-09-06 17:03 ` Ed W
2005-09-06 17:21   ` Ciaran McCreesh
2005-09-06 20:07     ` Alec Joseph Warner
2005-09-11 23:53     ` Ed W
2005-09-12  0:03       ` Ciaran McCreesh
2005-09-12 17:04         ` Ed W
2005-09-12 17:19           ` Michael Kohl [this message]

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=20050912191936.73ca6a75@localhost \
    --to=citizen428@gentoo.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