From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] User ebuilds: all developers, please read this
Date: Mon Jul 30 14:57:02 2001 [thread overview]
Message-ID: <0107302357590L.00612@localhost> (raw)
Hi all,
I have taken on myself the management of incoming ebuilds from users without
cvs accounts. The ebuilds will (for now) still be posted here.
Ebuilds go into /usr/portage/incoming. I will create low-priority, public
unstable dev-wiki notes to the teams involved for each ebuild.
Developers should test ebuilds, classify them and move them to their new home
(and delete them from incoming). To keep track of the situation I suggest
that whenever a developer verifies a user ebuild, he should grab the wiki
item (and mark it completed or not as needed).
On the mailing list, I will post std. notes as replies to the ebuilds I move
to /usr/portage/incoming.
--
Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel
next reply other threads:[~2001-07-30 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 14:57 Dan Armak [this message]
2001-07-30 18:51 ` [gentoo-dev] User ebuilds: all developers, please read this Chad Huneycutt
2001-07-31 0:47 ` Dan Armak
2001-07-30 20:44 ` Parag Mehta
2001-07-30 20:59 ` Daniel Robbins
2001-07-31 0:48 ` Dan Armak
2001-07-31 8:32 ` Ben Lutgens
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=0107302357590L.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