From owner-cvs-ports Wed Aug 12 03:49:20 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09474 for cvs-ports-outgoing; Wed, 12 Aug 1998 03:49:20 -0700 (PDT) (envelope-from owner-cvs-ports) Received: from ns11.rim.or.jp (ns11.rim.or.jp [202.247.130.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09170; Wed, 12 Aug 1998 03:47:23 -0700 (PDT) (envelope-from masafumi@aslm.rim.or.jp) Received: from rayearth.rim.or.jp (rayearth.rim.or.jp [202.247.130.242]) by ns11.rim.or.jp (8.8.5/3.5Wpl2-ns11/RIMNET-2) with ESMTP id TAA16139; Wed, 12 Aug 1998 19:46:58 +0900 (JST) Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP id TAA06005; Wed, 12 Aug 1998 19:46:58 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by mail.aslm.rim.or.jp (8.8.8/3.5Wpl3-SMTP) with ESMTP id TAA05358; Wed, 12 Aug 1998 19:26:45 +0900 (JST) To: scrappy@FreeBSD.ORG Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-ports@FreeBSD.ORG Cc: max@wide.ad.jp Subject: Re: cvs commit: ports/devel/mico-latest - Imported sources From: Masafumi NAKANE/=?iso-2022-jp?B?GyRCQ2Y6LDJtSjgbKEI=?= In-Reply-To: Your message of "Sun, 12 Jul 1998 00:27:27 -0700 (PDT)" <199807120727.AAA05095@freefall.freebsd.org> References: <199807120727.AAA05095@freefall.freebsd.org> X-Mailer: Mew version 1.92.4 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980812192644M.masafumi@aslm.rim.or.jp> Date: Wed, 12 Aug 1998 19:26:44 +0900 X-Dispatcher: imput version 971024 Lines: 15 Sender: owner-cvs-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > scrappy 1998/07/12 00:27:27 PDT > ports/devel/mico-latest - Imported sources > Update of /home/ncvs/ports/devel/mico-latest > In directory freefall.freebsd.org:/d/users/scrappy/mico-latest > Log Message: > This brings in a seperate mico port, of version 2.1.0. The previous port > is "frozen" at 2.0.5 due to requirements based on the Gnome project, after > checking with the MAINTAINER of said port about upgrading. I thought this kind of situation requires repository-copy of the existing port prior to making another version available in the tree? Cheers, Max