Ben Collins-Sussman <sussman@collab.net> writes:
> Yes, this would require major new design to the repository. At the
> moment, we have exactly one mechanism for "versioning" anything, whether
> it be files, directory structure, or file/dir metadata: sequential
> revision trees.
>
> The problem is, the trees themselves have metadata (datestamps, author,
> and log messages). If you want to version *that* metadata, how do you
> do it?
Most of that metadata one doesn't want to touch. If datestamps,
author, etc. were made read only, and log messages were somehow
treated specially, we'd probably eliminate the problem -- i.e. if all
unversioned properties were read-only and somehow logs were treated
specially.
However, ignoring that for now, is there any sort of hack that could
be added so that (for now) changes to the unversioned properties
showed up in incremental files? That would get rid of a lot of my
immediate issue.
Perry
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 19 17:26:39 2004