From owner-freebsd-current Tue Jul 15 00:08:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA10994 for current-outgoing; Tue, 15 Jul 1997 00:08:42 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA10989 for ; Tue, 15 Jul 1997 00:08:39 -0700 (PDT) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id CAA09504; Tue, 15 Jul 1997 02:08:27 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <19970715012130.45333@keltia.freenix.fr> References: ; from Richard Wackerbarth on Mon, Jul 14, 1997 at 04:35:59PM -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 15 Jul 1997 02:07:41 -0500 To: Ollivier Robert From: Richard Wackerbarth Subject: Re: CTM and the Attic Cc: freebsd-current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >According to Richard Wackerbarth: >> The tree as distributed by CTM is just the same as you get by running CVSup >> on the CVS tree and, for 2.1, 2.2, and current, doing a CVS checkout >> against the appropriate tag. Files which are deleted get a one line entry >> in the CTM delta to tell ctm to delete the target file. > >The main problem with CTM is when large number of files are deleted. The >deleted files end up in the Attic but get transmitted. Problem is that the >delta generation has no concept of "a file being moved"... The last time that I looked, CVSup still had the same problem. Perhaps the "problem" is that such movement should not occur in the first place. Don't blame the messengers.