Hi James, I agree - we should keep the HEAD as the main development line, and make a Xerces-2.7 branch as suggested.
I'll try to explain the tagging thing a bit more clearly. James Berry <[EMAIL PROTECTED]> writes: > The reason for a branch-point tag is that it gives you an easy way to > get diffs of all changes made on the branch, since the branch-point. > I don't believe there's any other way to do that, unless you memorize > the revision number of the branch point...which is what the branch- > point tag really does for you ; In SVN branches and tags are identical except for their names - there are no tags or branches in SVN - just copies. A tag or a branch is simple a copy of some part of the repository tree as it looked at a given snapshot in time - but unlike CVS that snapshot is not frozen, both tags and branches can be committed to. They are both created by using the 'svn copy' command with a source and a destination URL: svn cp http://host.name/svn/product/trunk \ http://host.name/svn/product/branches/product-3.0 svn cp http://host.name/svn/product/trunk \ http://host.name/svn/product/tags/product-3.0 In SVN, it is only social convention that makes us call it a tag or branch. The idea of tags is that you want to keep it read-only historical copy, and the branch is something that you plan to develop further. Technically they are identical except for their name. The "tag the branchpoint to make merging easier" is done in SVN by giving an informative commit message, so that you can use 'svn log' and locate the revision number that started the branch. This all explained much better than my simple attempt in the SVN manual, Chapter 4. Branching and Merging. HTH, jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
