From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from HERMES.genomatica.com (neuromancer.genomatica.com [12.105.233.242]) by chiba.3jane.net (Postfix) with SMTP id AAB79ABD7E for ; Fri, 31 May 2002 11:26:04 -0500 (CDT) content-class: urn:content-classes:message Subject: RE: [gentoo-dev] Hard Work for ARGGHH... (Future ebuild List) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 31 May 2002 09:25:22 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [gentoo-dev] Hard Work for ARGGHH... (Future ebuild List) Thread-Index: AcIIrY6wrNmMk/GsRASsplvKixgxQQAEeqzg From: "Sean P. Kane" To: Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: d8acb2bd-0708-4ea7-9a59-783f190bbb52 X-Archives-Hash: eba06c8516b5afb310d2d8ddeae8ecd7 I agree this would be a very nice feature and could be kept on the gentoo.org site as a list of ebuilds in progress, email address of developer, and status. This could at least allow people to try and contact the person who has started the ebuild, and decide whether they want to try and do there own, help with the current one, or wait for it to be completed. Sean -----Original Message----- From: Alexander Gretencord [mailto:arutha@gmx.de]=20 Sent: Friday, May 31, 2002 07:07 To: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] Hard Work for ARGGHH... (Future ebuild List) On Friday 31 May 2002 15:52, hanez wrote: > is it possible to make a list under gentoo.org where all the gentoo=20 > devs are making entries of there ebuilds and maybe the=20 > completion-status, they are working on at the moment? I've had something similar. I made an ebuidl which was put into "resolved=20 later" state because the dev's had no time. Then some time later another ebuild for the same software gets in. I didn't even notice because noone marked my ebuild as outdated or anything. I just noticed because some other=20 dev saw my old ebuild and marked it as old when he saw it hanging around while some newer ebuild got in. I think this should be really improved. Also if someone makes an ebuild check=20 if there is one in bugzilla already and then check your ebuild in under the=20 same bug id as a new version or make a pointer to the old one. Alex --=20 "They that can give up essential liberty to obtain a little temporary safety=20 deserve neither liberty nor safety." Benjamin Franklin _______________________________________________ gentoo-dev mailing list gentoo-dev@gentoo.org http://lists.gentoo.org/mailman/listinfo/gentoo-dev