"bryce_nesbitt" <[EMAIL PROTECTED] <http://mail.gnu.org/spam.html>> writes:
/I'd like CVS to enforce treating these six files as one atomic/ /object, with a single revision history./
You could put them into an archive (eg tar) and check that in. Then your build system would be in charge of unpacking the archive into its constituent files when necessary. I'm guessing that the files are not hand-editable anyway.
But if the files are themselves generated by some tool from another file, it's that original source file that should go into CVS, not the generated files. -Ed Avis
That's a good suggestion. And if I use an uncompressed archive format, I might even get good delta storage efficiency.
-Bryce
(In this case, my originals are a set of related binary application documents. In other projects I like to use CVS for storage of the generated target binaries, AND the binary tools that created them. There's no telling what, a few years down the road, you'll actually be able to get to work.)
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
