  Re: svn commit: propchange - r17029 - svn:log  From: Kalle
Olavi Niemitalo <kon_at_iki.fi> Date: 2005-10-26 21:42:36 CEST
Kobayashi Noritada <nori1@dolphin.c.u-tokyo.ac.jp> writes:  >
Should we make logs versioned and make it conflicted or merged
when > editted at the same time?? :-)  Why, of course! I'm
thinking of the following goals: * Let SVK mirrors of a
repository receive revprop changes with   reasonable efficiency
(i.e. not rescanning the whole history   in every sync). *
Detect conflicting changes of revision properties. * Allow (but
don't require) log entries for revprop changes. * If a revision
property has been changed, then reading that   property should
by default return the most recent value,   as the change was
intended to retroactively affect history. * Preserve all
previous values of the revision property   somewhere, until they
are explicitly obliterated. * The history of how a revision
property was altered can itself   be recursively altered.  So,
how about this scheme: * Each revprop c