|
From: | Andrew Stewart |
Subject: | new release, replace older release files |
Date: | Mon, 8 Jan 2007 13:40:05 -0500 |
I'm familiar with basic CVS functioning, but when it comes to managing 'releases', etc., I'm still a little hazy. Here's my situation: I have a module which represents a project I'm working on containing a set of files. I have completely rewritten the 'project', however, so the project as it 'used to be' (ie: the old files) are no longer necessary and I'd like to replace them with the set of new files (the project 'as it is').. but I obviously want to keep the old files in history. I'm not really sure how best to go about this. Should I 'cvs remove' the older files and then add the new files under a new release tag? Basically I'd like to be able to go back at any time and retrieve either the older version of the project or the current one according to a release tag (say, beta 1 or beta 2). Can anyone share with me the what the 'conventional' way of doing this would be? Thanks!, Andrew -- Andrew Stewart Research Assistant, Genomics Team Navy Medical Research Center (NMRC) Biological Defense Research Directorate (BDRD) BDRD Annex 12300 Washington Avenue, 2nd Floor Rockville, MD 20852 email: address@hidden phone: 301-231-6700 Ext 270 |
[Prev in Thread] | Current Thread | [Next in Thread] |