From: Einar Karttunen <ekarttun@cs.helsinki.fi>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Proposal for an unstable branch
Date: Mon, 4 Mar 2002 08:41:34 +0200 [thread overview]
Message-ID: <20020304064134.GB17581@shellak.helsinki.fi> (raw)
Hello
Now as the freeze is coming along I was thinking
that we could have an unstable branch, wich would
be for development ebuilds which are not considered
stable enough for the "stable" distribution yet.
Currently unstable ebuilds are avaiable either
masked in the portage tree, or from the authors
homepage, which is quite unconvenient if I want
to check whether someone has already worked
on some app.
The submittal of ebuilds to the unstable tree could
be made easier than to the stable tree, so the
core developers would not be forced to confirm
each upload. The unstable tree would of course
not be officially supported. This would also
solve the problem about development versions
in the stable portage tree.
- Einar Karttunen
next reply other threads:[~2002-03-04 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 6:41 Einar Karttunen [this message]
2002-03-04 11:05 ` [gentoo-dev] Proposal for an unstable branch 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
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=20020304064134.GB17581@shellak.helsinki.fi \
--to=ekarttun@cs.helsinki.fi \
--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