Ryan Schmidt wrote:
> On Dec 19, 2005, at 20:45, Phil Endecott wrote:
>> Granse, Erik (STP) wrote
>>> - Revision properties are a possibility, but we'd want to associate
>>> the property to a specific file. Conversely, file properties don't
>>> allow us to also associate the property to the file at a specific
>> On the contrary, file properties are associated with particular
>> revisions. You can set a "status" property to "approved" and commit
>> it, and it's that particular revision that is affected. Subsequently
>> you can change the status property to "released" and commit that.
>> The log will show you which properties changed in which revisions.
> Phil, I'm pretty sure Erik had it right in the first place. There are
> two kinds of properties in Subversion:
> * Versioned properties are attached to specific files and directories,
They are recorded for particular revisions of particular files and
directories. Through a file's history, its properties can change. If
you look at an old revision of a file you'll see the properties that
applied at that time. This gives the sort of per-file status record
that Erik needs.
> and to apply or remove them, you increase the repository revision
Erik, why is it important to you that the revision number doesn't change
when you change the status of a file? It seems like an unnecessary
restriction to me. Perhaps you are putting too much value on the
repository revision number. It is just a number.
I think what you need is what many people do when we declare that a file
or feature is "frozen", "stable", "approved" etc. Setting properties on
files to indicate this is a good way to solve the problem. You can
write yourself a script that will call "svn propget" and show you the
status of a file, find files that don't have a particular status, etc.
You can also have hook scripts that would, for example, allow only
certain users to change files that are "frozen".
(I'd be interested to see if any of the web-based repository browsers
can view properties to support this sort of thing, e.g. colour-coding
files based on status.)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Dec 20 00:38:34 2005