Suppressing log suppression (down with the -l switch)
Larry Jones
>
> One
> question, though: does cvs -l suppress filtering through loginfo?
No. The only thing it does is prevent writing to the history file.
-Larry Jones
There's a connection here, I just know it. -- Calvin
Brian Lenihan
> Rob Lanphier writes:
>>
>> One
>> question, though: does cvs -l suppress filtering through loginfo?
> No. The only thing it does is prevent writing to the history file.
I'm not sure why you are suggesting loginfo and friends will solve the
problem as they only get triggered for commits.
Loginfo for is fine for notification purposes, but it is not a
substitute for the cvs history which contains all the transactions,
not just the commits. It should be a reasonable assumption that the
entire history is available, including checkouts, updates, tags,
exports, etc.
History logging is enabled by default if the cvs init command is used
to create a repository. It makes little sense to me for users then to
have the ability to disable history logging from the client side.
My opinion is that clients should not be able to tell a server to look
the other way. I am unaware of any other servers which allow clients
to disable logging on the server side.
In case there is some valid reason to disable history logging which I
am unaware of, it would be nice if it was a configurable option. A
CVSROOT/config keyword would be much nicer than a compile-time or
configure option. Otherwise, the -l flag should be removed
completely.