From owner-freebsd-current Wed Sep 4 11:59:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA26957 for current-outgoing; Wed, 4 Sep 1996 11:59:34 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA26951 for ; Wed, 4 Sep 1996 11:59:27 -0700 (PDT) Received: from eel.dataplex.net by mail.crl.com with SMTP id AA28754 (5.65c/IDA-1.5 for ); Wed, 4 Sep 1996 11:57:56 -0700 Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id NAA04445; Wed, 4 Sep 1996 13:55:34 -0500 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 4 Sep 1996 13:55:34 -0500 To: John Polstra From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Latest Current build failure Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I was thinking some more about an idea Jordan brought up: > >> Actually, all you'd need to do is have your cvsup file modified to >> use a specific date in updating a previously checked out version >> of HEAD. > >Here is a related idea I've been toying with. I think I could easily >extend CVSup to support "pseudo-tags". > The cutoff date could be read from a configuration file on the server. The cutoff date can also be distributed. >That seems better than asking the users to change their cutoff dates all >the time. Why so? The same mechanism that selects the cutoff date on the server can be automatically applied at the user's end. There is no penalty for the user to "pre-fetch" additional updates. In fact, they might be useful.