From owner-freebsd-hackers Sun Sep 1 14:22:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA19459 for hackers-outgoing; Sun, 1 Sep 1996 14:22:41 -0700 (PDT) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA19448 for ; Sun, 1 Sep 1996 14:22:36 -0700 (PDT) Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id QAA11046; Sun, 1 Sep 1996 16:21:43 -0500 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 1 Sep 1996 16:21:44 -0500 To: "Philippe Charnier" From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: ctm: moving file to Attic Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Philippe Charnier" writes: >For now, when a file go to the Attic, something like this is run and >the content of the entire file is sent via ctm. >The problem is maybe: How to keep timestamp in sync? I fear that you was "out-of-luck". YOU can recognize that something was moved in a particular context. However, CTM is a more general purpose "mirroring" mechanism. There is the general problem of recognizing that a "tree" has been modified, at least in part, by moving or copying something already in the tree. Since CTM simply comes along and looks at the current state of things, it doen't get many "hints" that a move took place. This is particularly true when the thing that was moved is also modified. I think that we would need an integrated modification/distribution system to make the workload reasonable for the program generating the updates.