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 firstname.lastname@example.org.
But the keyword is still getting expanded in this file. I can't figure it out as it seemed as if things were working ok locally, but maybe it just didn't expand it locally but did expand it on the server. At any rate, when I deleted my sandbox and checked out the module again the keyword was expanded. I wanted to be able to selectively turn off keyword expansion on certain files and have it stay that way. At this point I'm going to edit CVSROOT\config and add KeywordExpand=i to turn it off globally. Thanks, Nick "Tony Hoyle" <tony.hoyle at march-hare.com> wrote in message news:ec47gj$m1q$1 at paris.nodomain.org... > Nick Duane wrote: >> While adding files to my CVS repository I found some files had keywords >> in them. I didn't want them expanded (third party source) so I put the >> file back to its original state and did: >> >> cvs update -ko <file> >> cvs commit -m "..." <file> >> > > Unless you do a commit -f the local expansion is not stored in the file. > This is to stop accidental changes of the expansion options. > > You could also redefine the keywords that are used in the 3rd party source > to be something else locally so you have both. > > Tony