On 13 Feb 2010 10:39:47, Stefan Küng wrote:
> On 13.02.2010 10:29, Stefan Fuhrmann wrote:
> />> There are two possible work flows: /
> />> /
> />> (1) Modify the external properties in the working copy, /
> />> then create the branch/tag from the working copy. /
> />> (2) branch/tag from a revision or HEAD in the repository, /
> />> then change the svn:external properties in the /
> />> repository, causing a new revision for each changed /
> />> property. /
> /> I would allow both workflows, depending on the path /
> /> we operate on (w/c or URL). /
> Sure, both will be allowed. I didn't mean this to mean 'either/or' but
> both with the user choosing which one to use.
> /> For case (2), it would be helpful to specify a depth /
> /> (root, children, infinite). Otherwise, it may take a very /
> /> long time to finish. In fact, it might be helpful to c/o /
> /> into a temporary working copy. /
> You mean this should also be done in the repo browser? I don't think
> that's a good idea:
> * would take way too long
> * would put a lot of stress on the server
> I like to limit this to the branch/tag dialog which is always started
> from a working copy.
I'm confused now. Workflow (1) is for working copy paths, right?
Workflow (2) is not supposed to flood the repo server with requests.
What does it do instead?
> />> Possible Development Stages /
> />> --------------------------- /
> />> /
> />> (1) Implement a svn:external parser which is able /
> />> to detect whether an external points to HEAD /
> />> or is already fixed. And allow modifying /
> />> the property to set a fixed revision. /
> /> I used svn_wc_parse_externals_description3() to parse the /
> /> externals definitions (see RepositoryLister.cpp). /
> I know :)
> Not sure if I can use the same though, since we don't have to just parse
> the externals but also have to modify them.
It seems the symmetrical "svn_wc_construct_externals_description()"
is missing. However, it is not difficult to write:
* use the svn_wc_parse_externals_description3 output as input
* make URLs as relative as possible
* issue one text line per external
> I'm still working out some details on how to handle the externals and
> the modifications. As soon as I have everything worked out, I'll start
I could use the same functionality for manipulating externals
in the repo browser.
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-13 22:50:19 CET