To turn off keyword expansion for an update, etc, use the -kk option, so cvs update -kk. However, my guess is that you want *.diff or whatever to always have keyword expansion supressed. In that case, you need to checkout the CVSROOT/cvswrappers as the repository administrator and add a line like this: *.diff -kk Now, on to my next question, why are you keeping patches in cvs? Since cvs can generate diffs which you can use to make patches, keeping patches themselves seems redundant. Normally, you would checkout the source, apply the patch, and checkin the modified code. The only exception that I have seen to this is the [FNO]BSD ports where there are BSD specific patches to the source which need to be maintained in the ports cvs because they are from the BSD teams, not from the original author. -Chris McKinley finger lamfada at lugh.net for GPG key On Fri, 8 Mar 2002, Bob Tanner wrote: > I have a patch in cvs, part of the patch looks like this: > > -# $Id: genbasedir,v 1.20 2001/11/30 20:40:27 kojima Exp $ > +# $Id: genbasedir,v 1.21 2001/12/12 14:50:43 kojima Exp $ > > The problem is when I commit the patch to cvs the $Id$ tag gets expanded thus > rendering the patch invalid. > > Anyway to make cvs not expand the $Id$ tag? > > -- > Minneapolis St. Paul Twin Cities MN | Phone : (952)943-8700 > http://www.mn-linux.org Minnesota Linux | Fax : (952)943-8500 > Key fingerprint = 6C E9 51 4F D5 3E 4C 66 62 A9 10 E5 35 85 39 D9 > > _______________________________________________ > tclug-devel mailing list > tclug-devel at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-devel >