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 email@example.com.
>>>> I add a text (-ko) and binary file (-kb). Then I want to commit to a >>>> revision: >>>> >>>> cvs commit -r 1.5 file.bin file.txt >>>> >>>> After commit, no file will have any keyword substitution at all. >>>> >>> Neither -ko or -kb have any keyword substitution, because you've just >>> explicitly switched it off for both of the files. The command is doing >>> exactly what you've told it to do. >> >> Are you saying this behaviour is as-designed? Then it must be a major >> design flaw. What has keyword substitution to do with revision number? >> >> Or wasn't I clear enough? Although both files where added with keyword >> substitution mode (-ko, -kb), both committed files have non (neither -ko >> nor -kb). > > I can't see your problem. You switch off the keyword substitution with - > ko > and -kb. So of course there is not substitution after commiting. No, no, this is not the problem. After adding both files, the corresponding CVS/Entries file contains these lines: /file.bin/0/dummy timestamp/-kb/ /file.txt/0/dummy timestamp/-ko/ After committing to revision 1.5, the lines loose the keyword substitution option: /file.bin/1.5/Mon Jun 16 07:53:41 2003//T1.5 /file.txt/1.5/Mon Jun 16 07:53:46 2003//T1.5 See here _____________________________^ Mike