Leo Davis wrote:
On Tuesday 11 April 2006 13:33, Leo Davis wrote:
On Tuesday 11 April 2006 12:58, Dirk wrote:
As I said, I'm not sure about file labels and version labels. There is
this "label promotion" feature [1] in VSS. But I'm not sure, whether
version labels take place within this label promotion feature. But
anyways, we could have two tags directories, one for "labels" and one
for "version labels".
The label promotion in [1] would be automatic with revision properties, as
making changes to the file doesn't change the property.
However, it doesn't provide a nice revision "snap" of code. In order to
do that, you'd reset the revision property when files get promoted.
Sorry, I wasn't really clear about what I was thinking of here. I'll use the
Microsoft example in [1]. So when MyProject (and all the files/directories
below it) get committed, it'll have some kind of revision property associated
with it with the contents:
Label:Version1
Comment:blah blah blah
When MyFile gets promoted we reset the revision property on *all* the
files/directories we labeled last time:
Label:Version1
Comment:blah blah blah
Promoted:MyFile on <date> <time>
or something like that.
Revision properties are exactly that; they apply to only the revision
you committed them in; I'm guessing you're referring to the versionable
properties?
I think having the properties will be handy but I would also like to
continue investigating the creation of some sort of "tags" folder as
well, due to the difficulty involved in "checking out by property" in
Subversion. One of the biggest benefits of a conceptual "label" is the
ability to go back and see how the code looked when that label was
applied, and storing this information only in properties will lose some
of that I think.
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
