[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Exporting only changed files from CVS
From: |
Spiro Trikaliotis |
Subject: |
Re: Exporting only changed files from CVS |
Date: |
Thu, 10 Jun 2004 08:48:45 +0200 |
User-agent: |
Mutt/1.5.6i |
Hello Jonathan,
* On Wed, Jun 09, 2004 at 07:33:17PM -0700 Jonathan Hurshman wrote:
> I am relatively new to CVS, having used Source Safe and StarTeam in the
> past. I am using CVS to track web development projects. I would like to
> be able to export from CVS into a directory where a non-CVS version of
> the application already resides, and have CVS only update new or
> changed files. Is this even possible?
My approach (I assume there are only text files, that is, files that can
be used with "patch"):
Whenever you make the non-CVS version, make sure you make a tag in your
CVS. For example, I assume the last non-CVS-version is tagged rel_1.
Now, if you want to generate a new one, run the following:
$ cd <CVS-version of your project>
$ # I assume you already have committed every change
$ cvs tag rel_2 # make the tag for the next upgrade
$ cd <non-CVS version of your files>
$ cvs rdiff -uN -r rel_1 -r rel_2 <cvsmodulename>|patch -p1
After this, your non-CVS version should be up-to-date
BEWARE! Make a dry run before doing that on the production server!
Futhermore, you might want to put the "rdiff" into a separate file
before applying patch.
HTH,
Spiro.
--
Spiro R. Trikaliotis
http://www.trikaliotis.net/
http://www.viceteam.org/