From: Thilo Bangert <thilo.bangert@gmx.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Proposal for an unstable branch
Date: Tue, 5 Mar 2002 14:33:34 +0100 [thread overview]
Message-ID: <20020305130255.5B2782005163@chiba.3jane.net> (raw)
In-Reply-To: <20020305060219.GA7463@shellak.helsinki.fi>
On Tuesday, 5. March 2002 07:02, you wrote:
> On 04.03.02 19:07 +0000(+0000), ian.c.smith@btinternet.com wrote:
> > Why not just unmask the ebuilds you are interested in?
>
> The problem is that the current system (submitting ebuilds
> via bugzilla) is too slow and requires too much effort from
> the developers, for a unstable branch.
>
this is excactly the problem, on the other hand it shows the good
things about gentoo: its growing, people are interested to help and the
main developers are trying to keep the distribution stable.....
lets not change any of that!
but maybe we still can address the problem
how about having a unstable.gentoo.org which is selfmanaged - if you
want a certain ebuild in the unstable tree, all you need to do is
register and add it. your then responsible until you give
maintainership to somebody else (or nobody, which would mark the
package unmaintained). also this tree is sync'ed with the stable gentoo
every hour. certain packages (maybe even categories) can not be
modified (ie. baselayout), those should stay in the stable branch.
or something like that...
> - Einar Karttunen
Thilo
prev parent reply other threads:[~2002-03-05 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 6:41 [gentoo-dev] Proposal for an unstable branch Einar Karttunen
2002-03-04 11:05 ` Thilo Bangert
2002-03-04 11:14 ` Einar Karttunen
2002-03-04 19:07 ` ian.c.smith
2002-03-05 6:02 ` Einar Karttunen
2002-03-05 13:33 ` Thilo Bangert [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=20020305130255.5B2782005163@chiba.3jane.net \
--to=thilo.bangert@gmx.net \
--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