Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: Gentoo Development <gentoo-dev@g.o>
From: Christian Faulhammer <fauli@g.o>
Subject: Re: [RFC] Improve policy of stabilizations
Date: Fri, 6 Nov 2009 18:18:01 +0100
Hi,

Ryan Hill <dirtyepic@g.o>:
> Is there any interest in allowing certain packages to be stabilized
> by the maintainer without going through the arch teams?  I always
> feel guilty when i file stabilization bugs for app-doc pkgs.

 I will not put any obstacles in the way, if you just do it for
packages with no processing.  Honestly, I do it for
x11-themes/claws-mail-themes because it only installs some graphic
files.

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://gentoo.faulhammer.org/>
Attachment:
signature.asc (PGP signature)
References:
[RFC] Improve policy of stabilizations
-- Arfrever Frehtes Taifersar Arahesis
Re: [RFC] Improve policy of stabilizations
-- Christian Faulhammer
Re: Re: [RFC] Improve policy of stabilizations
-- Markos Chandras
Re: [RFC] Improve policy of stabilizations
-- Christian Faulhammer
Re: Re: [RFC] Improve policy of stabilizations
-- Ben de Groot
Re: Re: [RFC] Improve policy of stabilizations
-- Joseph Jezak
Re: [RFC] Improve policy of stabilizations
-- Ryan Hill
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: [RFC] Improve policy of stabilizations
Next by thread:
Re: [RFC] Improve policy of stabilizations
Previous by date:
Re: [RFC] Improve policy of stabilizations
Next by date:
Last rites for dev-ruby/qt4-qtruby


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.