NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Is it really a problem? (Score:2)
I agree, allowing tags to be mutable is silly, but has that actually been a problem for you in practice. I don't recall ever actually modifying the contents of stuff under a tag, and you can always revert it.
As far as the checkout thing goes, that'd be annoying, but I've never done that either. When I want to make a tag I always operate directly on the repo URI:
svn cp http://.../svn/Foo/trunk [...] http://.../svn/Foo/tags/2.0 [...]Yeah, distributed VCS is probably better in lots of ways, but Subversion works well enou
Re:Is it really a problem? (Score:1)
I updated the code to tag directly in the repo. The obnoxious thing is that now there are two operations: update the trunk with the new release iformation, then tag. It is not atomic. I have to specify what changeset to copy into the tag.
rjbs
Reply to This
Parent
Re: (Score:2)
Uh, shouldn't you check in the "bump version" change to trunk _before_ you tag said version?