Re: Special support for tags and branches

Hi,

hakon@ion.no wrote:
> In Subcommander, the user has to write the tags- and branches- URL, in
> addition to the trunk URL. (Or click on a 'standard project layout' button
> to choose the common tags/, branches/ and trunk/ layout.)

You don't have to set the urls but it helps when creating new branches
and tags in the most common case.

> Have you
> received any feedback on the need to write in the three URLs? Is that why
> you put in a 'standard project layout'?

It's just a convenience function for those that use the subversion layout.
I don't know if anyone is really using it.

> How do you Martin, as a Subcommander developer, view my suggestion that
> Subversion should standardize on using properties to locate the tags- and
> branches- directories, and to use properties to mark a tag (in the tags
> directory) and a branch (in the branch) directory?

I don't know. Thinking more about it, subversions copy tags offer a lot
of flexibility and it is not so easy to provide a "simple" interface.

Another example. At work we have a layout that looks something like this:

/tags
   /2.10.1
   /2.10.2
   /2.10.3
/branches
   /2.10.x
/trunk
/vendor
   /xercesc
      /current "trunk"
      /2.6.0 "tag"
      /2.6.1 "tag"

The trunk/branches/tags is the standard layout. Branches are made by copying
/trunk to /branches/<name> and tags are made by copying /trunk or
/branches/<name> to /tags/<name>.

Now the interesting part is the vendor branch. The /current path is similar
to /trunk for the vendor library. New versions are checked in on the /current
path. But the tag for the new version is not placed in the /tags path but
alongside the /current path (the 2.6.0, 2.6.1). So the destination of a tag
depends on the source of the tag.

So there is no way to handle both tag operations with a single tags location.

-- 
Martin
Subcommander 1.1.0 - http://subcommander.tigris.org
a cross platform Win32/Unix/MacOSX subversion GUI client & diff/merge tool.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org