public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hendrik Visage <hvisage@envisage.co.za>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Organizing user ebuild submissions
Date: Mon Jul 30 19:33:01 2001	[thread overview]
Message-ID: <20010731033201.O12071@hvs.envisage.co.za> (raw)
In-Reply-To: <0107302353340K.00612@localhost>; from danarmak@gentoo.org on Mon, Jul 30, 2001 at 11:53:34PM +0300

Perhaps think of a gentoo-ebuild mailing list??
this way the -dev group could discuss development issues rarther than ebuild
troubles/submissions.

On Mon, Jul 30, 2001 at 11:53:34PM +0300, Dan Armak wrote:
> On Monday 30 July 2001 23:46, you wrote:
> > Dan Armak <danarmak@gentoo.org> writes:
> > > Good idea.  Dan, go ahead and create and add a /usr/portage/incoming
> > >
> > > >directory to CVS and check all new ebuilds in there.  Then, post a
> > > >wiki item for each new ebuild (or batch of related ebuilds) and
> > > >assign the wiki item to the appropriate team, priority "low".  Thanks
> > > >for doing this.
> > >
> > > OK. Should I classify the ebuilds as well and have e.g.
> > > /usr/portage/incoming/app-text?
> >
> > Isn't it better if the team (which should have the best idea of where
> > it should go) put them in the right directory? That will also make it
> > easier on the one that puts them in incoming.
> Who is me. Fine then! I'll collect the ebuilds posted in the last week or so, 
> which is what I have of the mailing list locally, and will add them to 
> incoming w/ wiki notes if they haven't been added already. Now we need to 
> notify all developers. I'll post a message on a new thread with a suitable 
> subject.
> 
> -- 
> 
> Dan Armak
> Gentoo Linux Developer, Desktop Team
> Matan, Israel
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev

-- 
------------------------
Hendrik Visage
hvisage@envisage.co.za



  reply	other threads:[~2001-07-31  1:32 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 [this message]
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=20010731033201.O12071@hvs.envisage.co.za \
    --to=hvisage@envisage.co.za \
    --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