> Perhaps what you *really* want is a "svn revpropfind" command which
> makes it easy to run queries against property data? This would
> make it relatively simple to do:
> svn co -r`svn revpropfind --firstonly eq svn:label Build_123 $URL` $URL
> Some of the metadata in the repository is a little hard to get at
> right now (read: not as efficient as it could be).
Yes, that would be awesome.
What *I* really want though is for a label to be a first class citizen.
There are any number of answers, I think, if we want to homebrew a solution.
What I, at least, really want to do is to feed Build_1 and Build_2 into the
text boxes of the diff command on WebFrontendX and have it do the right
Both the traditional tags and branches have the same sort of problem. Even
good programs like TortoiseSVN that even have an option to tag branch don't
prompt you with the right location when you choose it. It would be nice to
maybe have an (officially blessed) property that lets you designate where
the proper location for the branches and tags directory, i.e. for Project1/
the tags directory is Project1/tags. That would enable things like "svn tag
foo.c" to do something sensible.
As it is now, there is no meta-data, everything is by convention, and the
conventions aren't strong enough to embolden tool creators to use them. :-)
Subversion implements tags in the same since that Windows Explorer
implements tags. You can designate a folder and copy things over there. (I
actually had a web developer that did that. He was puzzled as to why I
wanted him to use our CVS system. I told him in case we needed to get back
to the code as it existed last week. At that point he showed me his
directory structure with nicely organized by date with copies of his code.)
That being said I would give several major portions of my anatomy for svn
revpropfind. I can think of half a dozen uses just off the top of my head.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed May 11 04:46:33 2005