Eric Siegerman [mailto:[EMAIL PROTECTED] wrote: > For the record, "cvs log" and "cvs status" can display different > values for the "-k" setting. The former is the value stored in > the ,v file. The latter is the "sticky" setting that's actually > in use in your sandbox; it will override the former if they > differ. Thanks for the correction, I should have mentioned 'log' to begin with.
> Or: > cvs admin -kb file # Change the setting in the ,v file > cvs update -A file # Propagate the change to the sandbox > # (yes, you do need the -A here) > Then check in a good copy of the file Ah, it's amazing how old habits stick. When I first learned how to get around this problem, I didn't have CVS admin privileges, and the "cvs admin" command could *only* be used by administrators. It was easier to remove/re-add the file than to track down an admin ;-) So, as a matter of habit I use the remove/add -bk route, even though I currently have admin privileges (and it seems you don't need them to use -kb now). -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
