From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: * X-Spam-Status: No, score=2.0 required=5.0 tests=DATE_IN_PAST_12_24,DMARC_NONE, FSL_HELO_NON_FQDN_1,HELO_NO_DOMAIN,INVALID_DATE,MAILING_LIST_MULTI, RDNS_DYNAMIC autolearn=no autolearn_force=no version=4.0.0 Received: from as1-4-5-1.han.s.bonet.se ([194.236.131.211] helo=fry) by cvs.gentoo.org with esmtp (Exim 3.30 #1) id 15RJxP-0003RG-00 for gentoo-dev@cvs.gentoo.org; Mon, 30 Jul 2001 14:48:07 -0600 Received: from fry (fry [127.0.0.1]) by fry (Postfix) with ESMTP id BCB6782523 for ; Mon, 30 Jul 2001 22:46:47 +0200 (CEST) From: Mikael Hallendal To: gentoo-dev@cvs.gentoo.org Subject: Re: [gentoo-dev] Organizing user ebuild submissions References: <0107302259100D.00612@localhost> <87d76i9n9q.fsf@codefactory.se> <20010730143027.S14345@cvs.gentoo.org> <0107302339040J.00612@localhost> Organization: CodeFactory AB In-Reply-To: <0107302339040J.00612@localhost> Message-ID: <878zh69mbs.fsf@codefactory.se> User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.0.103 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: gentoo-dev-admin@cvs.gentoo.org Errors-To: gentoo-dev-admin@cvs.gentoo.org X-BeenThere: gentoo-dev@cvs.gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@cvs.gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Mon Jul 30 14:49:01 2001 X-Original-Date: 30 Jul 2001 22:46:47 +0200 X-Archives-Salt: 79cb9912-0131-4a1d-a39f-3b7684366a74 X-Archives-Hash: 028a76895854f3151b3fa6ee2010af76 Dan Armak 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. Regards, Mikael Hallendal -- Mikael Hallendal                micke@codefactory.se CodeFactory AB                  http://www.codefactory.se/ Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918