From owner-freebsd-current Tue Oct 8 04:37:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA20672 for current-outgoing; Tue, 8 Oct 1996 04:37:09 -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 ESMTP id EAA20665 for ; Tue, 8 Oct 1996 04:37:06 -0700 (PDT) Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.7.5/8.7.3) with ESMTP id GAA08613; Tue, 8 Oct 1996 06:35:38 -0500 (CDT) X-Sender: rkw@eel.dataplex.net Message-Id: In-Reply-To: <57ohidg328.fsf@tees.elsevier.co.uk> References: Jake Hamby's message of Fri, 4 Oct 1996 13:50:53 -0700 (PDT) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 8 Oct 1996 06:34:23 -0500 To: Paul Richards From: Richard Wackerbarth Subject: Re: Wow, CVSup is cool! Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >My desire for this is that I needed to go out and got caught up trying >to determine which deltas were missing and getting odd files one at a >time. I really wanted some mechanism that I could just leave running >while I was out that knew to grab the missing/damaged files. Sup was >actually quite good at that function and as a one off recovery >mechanism would still be useful. > >Anyone else think this would be useful? Since this is an infrequent use, it is not worthwhile to support it with a mechanism as heavy as sup. I suggest that you use "mirror" for this. By setting the appropriate include/exclude rules, you get just the files that you want. In my own case, I do not get every base delta. It is "cheaper" for me to simply keep a few more files to carry me back to an earlier delta. What I would like to see is coordination between the sup disptibutions and the ctm distributions so that you can seamlessly use sup to "fix" a tree and ctm to routinely update it, or vise versa.