Timothee Besset <ttimo@idsoftware.com> writes:
> If you don't svn tag your new branch right after creation, you have to svn
> log it and find out what revision number to use as the start point. Not
> sure wether or not there should be a command or a revision syntax to point
> to the 'branch creation' revision.
Yup. That's why we need to solve the "repeated merge" problem
someday. Humans shouldn't have to remember the exact revision in
which a branch was created, or remember exactly which revisions have
been merged from one branch to another. Someday Subversion will
automate that knowledge for you, probably by tracking the info in
properties.
> Another thing I'm seeing, is that the concept of branches versus tags in
> svn is very artificial. I think we like to talk about branches and tags
> because we've spent too many years working with cvs.
Well, the terms "branch" and "tag" are universal SCM terms. They're
not unique to cvs. They're general concepts that are still useful to
everyone. Subversion just happens to implement both concepts through
copying.
> In that regard, I think it would make sense if the location in repository
> where the admins decide to store tags would be only available to branch
> creation and removal, but not 'modifications'. This is strictly to enforce
> a difference between the tag and branch concepts, and to be safe from
> wrong manipulations.
Um, yup. That's exactly what the svn Book has always said. If admins
don't trust users to remember to treat a tag directory like a tag,
then they can use an access-control script to only allow "cp" and "rm"
within the /tags area. As Rafael mentioned, we have both a perl and
python script for fine-grained access control.
But let me remind you of something: if somebody *does* accidentally
commit a change to a tag directory, who cares? Just undo it, and
scold the user. This is version control. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 24 15:14:59 2002