bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Suppressing log suppression (down with the -l switch)


From: Chris Bohn
Subject: Re: Suppressing log suppression (down with the -l switch)
Date: Thu, 08 Apr 2004 17:26:51 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113

I found an old posting of the same subject:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=mailman.5904.1052547663.21513.bug-cvs%40gnu.org&rnum=1&prev=/groups%3Fq%3Dcvs%2520disable%2520history%2520option%2520removed%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26sa%3DN%26tab%3Dwg

The reason this should be kept or at least controlled by a config option is backwards compatibility. This is yet another case where a new version of cvs is going to cause me headaches because backwards compatibility was not considered enough.

We have a number of scripts that call cvs commands. Those scripts are run on a very frequent basis based on user input, and most of them use the -l option to disable history logging because it is an automated process. We know it works, and we don't want to clutter the history file with actions from it (we just want user actions). Now the option is gone, and if we want to upgrade from our locally modified 1.10 cvs version to 1.12.6, we have to go through all of these scripts and yank out the -l option. Had the behavior instead been an option, we could just set the option on, and others that didn't like it could turn it off. It would have been easy for everyone and backward compatible. As it is now, the differences from 1.10 to 1.12.6 are significant. Because of other backward compatibility issues, we are going to make a whole test bed just to upgrade cvs, which shouldn't be needed. We have to make a new cvsroot because many files changed formats and generate errors/warning about them:

cvs commit: warning:  Set to use deprecated info format strings.  Establish
compatibility with the new info file format strings (add a temporary '1' in
all info files after each '%' which doesn't represent a literal percent)
and set UseNewInfoFmtStrings=yes in CVSROOT/config.  After that, convert
individual command lines and scripts to handle the new format at your
leisure.

cvs commit: warning: commitinfo line contains no format strings:
   "perl /cvs/root/CVSROOT/X"
Appending defaults (" %r/%p %s"), but please be aware that this usage is
deprecated.

We don't want end users seeing these, so we have to fix them first and test all the changes. We also have to duplicate our automated scripts and remove references to -l options and anything else we find to no longer work. I think backwards compatibility is important and should be a bigger priority with cvs.

Chris





reply via email to

[Prev in Thread] Current Thread [Next in Thread]