From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Organizing user ebuild submissions
Date: Mon Jul 30 14:32:01 2001 [thread overview]
Message-ID: <0107302332560I.00612@localhost> (raw)
In-Reply-To: <87d76i9n9q.fsf@codefactory.se>
On Monday 30 July 2001 23:26, you wrote:
> Dan Armak <danarmak@gentoo.org> writes:
> > I wouldn't mind handling the mailing-list side of the story - grabbing
> > all ebuilds and putting them wherever and informing whoever. But many
> > ebuilds come through for packages I don't use and in many cases can't
> > test. I don't think any one developer could or should handle the
> > testing, that's why we have teams. We can have an "incoming" ebuild
> > tree (in cvs or elsewhere) and developers could grab ebuilds that fall
> > under their area of interest, test them and put them either in the
> > stable or unstable cvs trees.
>
> I also think this is the way of doing it. Perhaps, when you find an
> ebuild in the mailinglist you can commit it to some place in cvs and
> add a wiki todo about it giving it to the correct team. This way it
> will be easy to track what "your" team has to test.
>
So, we come again to the requirement of introducing stable/unstable/user etc.
development trees into cvs.
--
Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel
next prev parent reply other threads:[~2001-07-30 20:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 13:58 [gentoo-dev] Organizing user ebuild submissions Dan Armak
2001-07-30 14:01 ` 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 [this message]
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=0107302332560I.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