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.)
Danny
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 13 18:55:58 2006