email@example.com wrote on 04/02/2004 08:50:41 AM:
> I'm just irresponsibly thinking out loud here...
> At first, I almost replied "You could set properties on the files, and
> use the properties as you use tags." Then I remembered that the
> properties would be carried forward to all future revisions of that
> file, until deleted. That doesn't quite do what you want.
> Then I thought: well, what if we had unversioned properties on files?
> Ah, but then they wouldn't work well with the normal 'update'
> mechanism. We still need the properties to be versioned, we just
> don't want them to propagate to future revisions automatically.
> So naturally, my third thought was: what about "ephemeral properties"
> that are automically removed on the next commit? That would get you
> the desired behavior, for both files and dirs.
> My fourth and fifth thoughts were, respectively:
> Ick, do we really want to implement that in Subversion?
> But wait, it would be easy to layer this as process on _top_ of
> Subversion. You can do it by choosing some conventions for the name
> and values of these properties, then have a pre-commit hook that
> checks to make sure the property is never carried forward. (You could
> also add some client-side logic in the form of wrapper scripts, to
> avoid the annoying rejection-from-server cycle in the first place --
> the pre-commit check would just be extra insurance.)
> I agree this is not as nice as having the support directly in
> Subversion, and I'd like to see where this discussion of labels goes.
> It's clear that there are some use cases not well-covered by our
> current feature set. However, in the meantime, this might be a
> workaround that can carry people through to the day when we do have
> some better solution (don't know whether that's 1.1, or 2.0, or later).
I just posted a reply to a similar message on the user list.
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.
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?
Received on Fri Apr 2 17:10:09 2004