Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> It's never been supported - that error is legacy from > well before the cvsnt project started. The date that > this patch was added is in 1997. But, but... I'm sure this was working under the 1.11.1.3 build we were using. No "not supported" errors and there were conflicts that resulted in two files like binary conflicts while keywords were still being updated in the files. Weird. So the answer is "it can't do that now" and probably wasn't doing it right before and we got lucky. Since this is the case, could the default cvswrappers file that is placed into new repository's CVSROOT directory get updated? A new 2.0.11 cvswrappers file claims -m, -t, -f and -k are all supported which is highly misleading. I appears like only -k is actually supported in CVSNT... Thanks for the quick response Tony, Aric # This file affects handling of files based on their names. # # The -t/-f options allow one to treat directories of files # as a single file, or to transform a file in other ways on # its way in and out of CVS. # # The -m option specifies whether CVS attempts to merge files. # # The -k option specifies keyword expansion (e.g. -kb for binary). # # Format of wrapper file ($CVSROOT/CVSROOT/cvswrappers or .cvswrappers) # # wildcard [option value][option value]... # # where option is one of # -f from cvs filter value: path to filter # -t to cvs filter value: path to filter # -m update methodology value: MERGE or COPY # -k expansion mode value: b, o, kkv, &c #