David Weintraub <qazwart@gmail.com> writes:
> 3). We want to be able to create labels, do diffs, etc., without
> having to bother with URLs Doing "svn diff -rFOO:BAR myfile.cc" is a
> heck of a lot easier than:
>
> svn diff http://myserver/repos/tags/FOO/dir1/dir2/dir3/myfile.cc
> http://myserver/repos/tags/BAR/dir1/dir2/dir3/myfile.cc
export FOO=http://myserver/repos/tags/FOO
export BAR=http://myserver/repos/tags/BAR
svn diff $FOO/myfile.cc $BAR/myfile.cc
> 4). Labels should be first class citizens. Creating a directory to
> represent a label is really a hack -- especially since you need a
> (so-far unpublished) hook to prevent someone from accidently changing
> what a tag points to in order to do this job correctly.
>
But you'd also need a way to change which revision your label refers
to, and hence a way to prevent someone changing your label... (surely
if you can't trust your users to leave the tags alone you've got more
problems than adding labels to subversion will support?)
>
> =====
> I think that the arguments made by the pro-label side for arguments 3
> & 4 are quite reasonable. Having to use a full URL just to do a diff
> can be a problem.
I see why labels are useful, but I dont understand why you don't just
write a shell script to do all this using properties (ie store the
labels in property on the repository root, and get the labels using
propget)
> 3). Have an "svn label" command as an alias of the "svn copy". Well,
> not quite an alias, but more of a shortcut:
>
> $ svn label FOO
>
> would be translated to
>
> $ svn copy <current URL> <URL>/tags/<path>
>
> or whatever is needed to actually create the tag directory.
>
> Sounds good?
isn't this trivial to do by hand (eg as a shell script)?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun May 8 13:48:59 2005