From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] Organizing user ebuild submissions
Date: Mon Jul 30 13:58:02 2001 [thread overview]
Message-ID: <0107302259100D.00612@localhost> (raw)
Hi all,
In the last few days there has been a edluge of ebuild submission on the
mailing list. I think we need to organize this process, because some ebuilds
get lost, and others may get grabbed by more than one developer.
A final solution could be, when we introduce stable/unstable trees into cvs,
we could add a "user" tree as well. Then ebuilds would move from user and
unstable into stable as developers find time to test them.
Until that happy time however we should make some temporary provisions. Is
anyone handling this issue specifically as of now?
--
Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel
next reply other threads:[~2001-07-30 19:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 13:58 Dan Armak [this message]
2001-07-30 14:01 ` [gentoo-dev] Organizing user ebuild submissions Daniel Robbins
2001-07-30 14:07 ` Dan Armak
2001-07-30 14:28 ` Mikael Hallendal
2001-07-30 14:31 ` Daniel Robbins
2001-07-30 14:38 ` Dan Armak
2001-07-30 14:49 ` Mikael Hallendal
2001-07-30 14:53 ` Dan Armak
2001-07-30 19:33 ` Hendrik Visage
2001-07-30 20:52 ` Daniel Robbins
2001-07-30 14:32 ` Dan Armak
2001-07-30 14:34 ` Daniel Robbins
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=0107302259100D.00612@localhost \
--to=danarmak@gentoo.org \
--cc=gentoo-dev@cvs.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