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.) Have you
received any feedback on the need to write in the three URLs? Is that why
you put in a 'standard project layout'?
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?
And what do you think of making special commands in Subversion for tagging
and branching, which utilizes the properties.
>>> 3. Clients should be able to locate and identify 'projects', branches
>>> tags. The need for this is exemplified by Subclipse
>> I think we should watch out with the word 'project'. Although both tags
>> and branches are our own ideas they have a basis in the SVN Cheap
>> Copies. A 'project' is what someone thinks is a single project. But it's
>> nothing tangible for SVN. I agree that we have such a thing as a
>> 'project' but without a clear definition we could think in different
>> (Probably just like the way we thought differently about tags ;) )
> I agree that 'project' is not well-defined. When I used the word 'Project'
> (with capital P) in the original email, I meant the collection of a trunk,
> its branches and its tags. I.e. it is a 'cut' or 'branchpoint' in the
> repository tree you want to tag or branch. This does not necessarily
> correspond to the user's perception of her project.
> In this case of Subversion, I like to think of
> "http://svn.collab.net/repos/svn" as the 'project URL'.
> But in the case of a /trunk, /tags and /branches layout, there is no
> simple 'Project URL'. If we are to follow other VCS' notion of such a
> 'Project', then the trunk defines the Project, because the branches and
> tags are hidden. This would mean /trunk/svn would be the 'Project URL'.
> A 'Project URL' is nice to have, because it defines the location of the
> trunk, tags and branches. So you could pass one URL to a GUI, and it could
> present you with a list of tags, a list of branches, and the immediate
> option of checking out the trunk.
By the way, Subcommander defines a 'project' in the exact same way. (But
Subcommander also puts working copies of the 'branchpoint' into the
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Jul 11 16:28:04 2006