[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Make cvs ignore some changes in files

From: Frederic Brehm
Subject: RE: Make cvs ignore some changes in files
Date: Thu, 22 Aug 2002 10:03:53 -0400

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

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 Brehm, Sarnoff Corporation, address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]