From owner-freebsd-hackers Sun Dec 1 15:28:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA05813 for hackers-outgoing; Sun, 1 Dec 1996 15:28:16 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA05808 for ; Sun, 1 Dec 1996 15:28:13 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id PAA23841 for ; Sun, 1 Dec 1996 15:28:13 -0800 (PST) Message-Id: <199612012328.PAA23841@austin.polstra.com> To: freebsd-hackers@freebsd.org Subject: CVSup vs. sup's "keep" keyword Date: Sun, 01 Dec 1996 15:28:12 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Recently somebody asked in -hackers how to make CVSup do something similar to sup's "keep" keyword or "-k" option. I'm so behind on that list that it expired out of my news spool before I had a chance to reply. I hope whoever asked is listening ... CVSup does not support sup's "keep" keyword. However, if you have a few files that you don't want CVSup to touch, there's an easy way to get what you want. The answer is in the "refuse" files, which are described near the end of cvsup(1). These allow you to make CVSup completely ignore certain files. The specified files will not be updated by CVSUp, nor will they be removed. They're simply ignored. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth