RE: Make cvs ignore some changes in files

[Frederic Brehm]

> From: Riechers, Matthew W
> > Again, why does something generated by a build need to be revision
> > controlled?


I wrote:

> The generated files don't need to be revision controlled, but they need to 
> be available to people or tools who cannot run the tool that generates the 
> files. The most convenient way to make the files available is to put them 
> into the repository alongside the other files that are also needed. The 
> side effect of this is that the files become revision controlled.

but then I wrote:

>  --- If these are different, then Makefile.cache is replaced with
>     the new version. The next cvs commit will commit the new
>     Makefile.cache along with any new or changed source files.


I just realized that this explains why, in this case, the files *must* be 
revision controlled. The new version of Makefile.cache corresponds to the 
new versions of the other files in the directory.

Fred

_____________________________________________________________________
Fred Brehm, Sarnoff Corporation, address@hidden
http://www.sarnoff.com/digital_video_informatics/vision_technology/index.asp