Re: "witty subject line about logging feature"

On Fri, 2005-07-22 at 16:49 -0400, Michael Sinz wrote:
> The goal should be that anything that plays with the repository should
> log

The goal of "keep track of everything which affected the repository" is
less important in an SCM like Subversion, because so much is already
intrinsically logged because of what we do. Also, it's already possible
to log write operations using hook scripts.

So, in some sense it's actually more important to add logging of read
operations than write ones. But as I argued earlier, it still only
really makes sense to log them when you're a server responding to
requests over a network connection.

(Rev-prop changes are not intrinsically logged right now, and must be
logged using hook scripts. But they should have history! Here's an
outline proposal of how to do it:

        Instead of modelling rev-props as a name -> value mapping, model
        them as a name -> list of (value, author, date) tuples. Figure
        out how to store the new model in a manner compatible with the
        old model. Provide access functions which access the entire
        list for a rev-prop; the existing access function will of course
        just return the value of the most recent tuple.

With that in place, it becomes much essentially unimportant to log write
operations, although once you have an access log it's natural to throw
them in.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 22 23:35:36 2005