On Fri, Jun 11, 2010 at 6:42 AM, Gary Hallmark <gary.hallm...@oracle.com> wrote: > All examples I have seen for tagging use svn copy (or svncopy -tag) to > create a tag. If I want to make sure nobody can change the tag, I guess I > could write a commit hook. But couldn't I use a versioned external > definition to create the tag instead of svn copy? Seems this would better > enforce that nobody can change the tag, since it isn't a copy at all. One > downside would be that if the tag contains unversioned externals, I would > not be able to pin them down, but I don't plan to have unversioned > externals. Are there any other downsides? > > Example: > trunk/ > tags/ > X -r123 ^trunk version_1.0
You would still need to enforce (via a commit hook) that no-one can modify the version_1.0 external definition to point to -r456 instead. Not sure how much simpler (or more difficult) this would be over having standard folders. BTW, I think the definition you might want to use is ^tr...@123, rather than -r123 ^trunk, but I could be wrong. Cheers, Daniel B.
