
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
Repository Basics
|
75
Revision and transaction properties are useful for associating information with a tree
that is not strictly related to the files and directories in that tree—the kind of informa-
tion that isn’t managed by client working copies. For example, when a new commit
transaction is created in the repository, Subversion adds a property to that transac-
tion named
svn:date—a datestamp representing the time that the transaction was
created. By the time the commit process is finished, and the transaction is promoted
to a permanent revision, the tree has also been given a property to store the user-
name of the revision’s author (
svn:author) and a property to store the log message
attached to that revision (
svn:log).
Revision and transaction properties are unversioned properties—as they are modi-
fied, their previous values are permanently discarded. Also, while revision trees
themselves are immutable, the properties attached to those trees are not. You can
add, remove, and modify revision properties at any time in the future. If you commit
a new revision and later realize that you had some misinformation or spelling error in
your log message, you can simply replace the value of the
svn:log property with a
new, corrected log message.
Berkeley DB
The data housed within Subversion ...