From owner-freebsd-ports Mon Jan 20 17:51:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA19340 for ports-outgoing; Mon, 20 Jan 1997 17:51:27 -0800 (PST) Received: from dfw-ix6.ix.netcom.com (dfw-ix6.ix.netcom.com [206.214.98.6]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA19335 for ; Mon, 20 Jan 1997 17:51:24 -0800 (PST) Received: from baloon.mimi.com (sjx-ca11-25.ix.netcom.com [199.182.128.121]) by dfw-ix6.ix.netcom.com (8.6.13/8.6.12) with ESMTP id RAA23279; Mon, 20 Jan 1997 17:50:37 -0800 Received: (from asami@localhost) by baloon.mimi.com (8.8.4/8.6.12) id RAA09454; Mon, 20 Jan 1997 17:50:25 -0800 (PST) Date: Mon, 20 Jan 1997 17:50:25 -0800 (PST) Message-Id: <199701210150.RAA09454@baloon.mimi.com> To: james@nexis.net CC: freebsd-ports@freebsd.org In-reply-to: (message from James FitzGibbon on Mon, 20 Jan 1997 09:11:11 -0500 (EST)) Subject: Re: For mSQL users... From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * > Why don't you import it as "msql-beta"? Then you can merge it into * > the main msql port when it comes out of beta. * * Not a bad idea. Who should I talk to about merging the CVS history in * when it's out of beta ? For this particular kind of merge, I don't think it is necessary to do anything about the CVS history. Just merge the last revision into the main msql port, all you will lose is the history on the msql-beta subtree, which I assume is not going to be much. FYI, if it's going to be merged in the other direction, i.e. if the new port is going to be called "msql2" or something and the old one is to disappear (like tcl/tk ports), then it is necessary to do a repository copy BEFORE importing the new port. Satoshi