Here's another one that seems to have fallen between the cracks. I was wondering if it would be useful to other CVS users to be able to define a .cvswrappers in a directory that applied to all files and subdirectories under it. This would allow one project to say ".doc" was binary and another to say it was text without having to have .cvswrappers files all through their trees. Thanks in advance..... :)hal mahaffey In a message dated 8/25/00 7:19:34 PM Eastern Daylight Time, [EMAIL PROTECTED] writes: << One of the biggest complaints I get when I try to sell CVS to our client development group is the lack of built-in binary detection. "cvswrappers" provides some support for this, but we've found something awkward with it: An extention considered "binary" by a Mac may not be binary to a Windows program, and vice versa. If this were only one extention in one module, the answer of course is to put the more populare one in the CVSROOT/cvswrappers file, and the other will simply have to be added to a .cvswrappers file in each directory a file of that extention appears in (or may appear in some day). Except, let's say that the less popular one has thousands of files in hundreds of directories. Wouldn't it be nice if, at the top of that particular module, I could put a ".cvswrappers" file that overrode the CVSROOT/.cvswrappers file? Or even specify a .cvswrappers.MODULE.NAME file in the "modules" file to be used for that purpose? Or SOMEthing? Luckily, SourceSafe stinks of death, which is making my selling job of CVS go somewhat easier, but it would be much better to address their concerns. Anyone willing to Patch for Money? :) :)hal mahaffey >> _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
