[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Dropping Subversion

From: <kfogel_at_collab.net>
Date: 2004-04-02 18:19:18 CEST

Mark Phippard <MarkP@softlanding.com> writes:
> I want to be able to use properties to store something like an issue/bug
> ID when I commit a change (by the way I wish this could be part of the
> commit just like a log message). I guess I am confused. I always thought
> that when I read that properties are versioned, that meant they only
> applied to the specific revision they were set for. It sounds like that
> is not the case. I assumed unversioned meant the property applied to the
> file, and versioned meant to a specific version of the file.

No, it's more subtle than that. "Unversioned properties" are
properties that

   - if you change them, look as though they've had the new value
     since the beginning of time

   - are not propagated to the "next instance" of whatever object
     they're attached to

Currently, Subversion's revision properties are this kind of
property. ('svn propedit --revprop -rXXXX svn:log', for example).

For the use case you're talking about, you should use revprops.
They're exactly what you want. The revision number *is* the handle on
the changeset, so you want a property attached to the revision
number. That's a revprop.

> Could properties be used for this? Let's say it could, does Subversion
> have the corresponding API's one might want to use in conjunction with
> using properties this way? For example, could I get a list of all files
> and versions that had a specific property/value pair set?

Not easily, no.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 2 19:31:56 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.