> hakon@ion.no wrote:
>> Exactly, and that's why the 'tags' location must be per directory. For
>> the
>> above example, there could be the following properties:
>> /trunk:
>> svn:tagslocation = /tags
>> svn:brancheslocation = /branches
>> /vendor/xercesc/current:
>> svn:tagslocation = /vendor/xercesc
>>
>> The user could give the URLs to /trunk and /vendor/xercesc/current, and
>> Subcommander could read off the locations for the tags and branches.
> Ok, this sounds good.
>
> Another thing: what should happen when someone selects a subdirectory
> from trunk to tag? Because you've indicated in 'trunk' with the property
> "svn:tagslocation" where tags will be stored, but we haven't done that
> for any subdirectories. (Or have we?)
>
> Do you want an error, tell them that there's no 'svn:tagslocation'
> information available, or should we look in parent directories for
> 'svn:tagslocation', or should we just let the user choose?
>
> (I'm just deepening out the idea a little, because I think we're on the
> right track here.)
If the user wants to tag a subdirectory, then that's another Project, as
per definition of 'Project' (mine and Subcommander's).
The Apache Software Foundation repository uses this technique of 'nested
Projects'. For example the Project /db/torque has a nested Project
/db/torque/common.
But if the user has not setup the subdirectory as a Project, then we
should give him an error message so he can act on it.
Håkon Hallingstad
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 13 22:40:17 2006