[Top][All Lists]

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

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

From: Derek R. Price
Subject: Re: Suppressing log suppression (down with the -l switch)
Date: Sun, 11 Apr 2004 17:45:17 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

Chris Bohn wrote:

I found an old posting of the same subject:


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.

If you'd like more say, feel free to follow the lists and make comment when we poll for suggestion. We often do before major changes.

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 bee

This was considered a security hole by some. Either you want logging or you don't. If you log for security and tracking purposes then it is trouble to allow any user to turn it off.

cvs commit: warning: Set to use deprecated info format strings. Establish compatibility with the new info file format strings (add a temporary '1' in

These changes were backwards compatible. They just make noise until you port forward. To mkae progress forward, we need to be able to ocassionally drop support for old features.

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.

That was part of the point of splitting stable and feature. When you have time you can make the major upgrade. Bug fixes are still available on stable.


reply via email to

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