From owner-freebsd-hackers Fri Nov 15 20:12:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA10178 for hackers-outgoing; Fri, 15 Nov 1996 20:12:53 -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 UAA10171 for ; Fri, 15 Nov 1996 20:12:46 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id UAA23915; Fri, 15 Nov 1996 20:12:33 -0800 (PST) Message-Id: <199611160412.UAA23915@austin.polstra.com> To: dgy@rtd.com Subject: Re: CVS Attic... Newsgroups: polstra.freebsd.hackers In-Reply-To: <199611160304.UAA07230@seagull.rtd.com> References: <199611160304.UAA07230@seagull.rtd.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Fri, 15 Nov 1996 20:12:33 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199611160304.UAA07230@seagull.rtd.com> dgy@rtd.com writes: > Greetings! > It's my understanding that a "cvs remove " should put > into the Attic subdirectory in the repository. Are there > conditions when this is *not* true? (i.e. *my* removes aren't > going to the Attic). Remember, the file in the CVS repository doesn't get changed until you do a "cvs commit" too. I suspect that is the cause of what you're (not) seeing. Also (I think this is right): Whether a file in the repository is in the Attic or not depends on the state of the head revision on the main (or default) branch. If you are working in another branch and do a remove, the file won't go into the Attic. In other words, a file can be "live" on some branches and "dead" on others. Attic residency is determined only by the state of the latest version on the main (or default) branch. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth