On Mon, Jun 16, 2008 at 11:39 AM, tejo dorus <tejodorus_at_hotmail.com> wrote:
>> Date: Mon, 16 Jun 2008 12:51:19 +0100
>> From: simon.tortoisesvn_at_googlemail.com
>> To: users_at_tortoisesvn.tigris.org
>> Subject: Re: SVNCopy from within TortoiseSVN
>> 2008/6/16 tejo dorus :
>>> As far as I can see, it (TSVN) should do exactly what the svncopy script
>> But you haven't said what that is.
> The exact behaviour of the svncopy.pl script is found in http://svn.collab.net/repos/svn/trunk/contrib/client-side/svncopy/svncopy.pl.in . What I expect to be done is:
> * Check out the tree and create a copy
> * For each "externals definition": find the head revision number in the external repository
> * Update the "externals definitions".
> * Commit
> BRANCHING (seems only to be working for "internals" (externals within the same repository)):
> 1. (Locally) copy the tree (ex: /Project/Project_Foo/Trunc) to the branch folder (ex: /Project/Project_Foo/Branch/BugFix)
> 2. (Locally) copy the "internals" (ex: /Project/Common) to the branch folder (ex: /Project/Project_Foo/Branch/BugFix/_Common)
> 3. (locally) update the externals definition, so that /Project/Project_Foo/Branch/Bugfix/Common points to /Project/Project_Foo/Branch/Bugfix/_Common.
> 4. Commit
> For step 2, the user should be able to choose which ones of the "internals" should be branched, and which ones should simply be tagged or perhaps remain pointing to the head revision. I imagine some kind of a checkbox list that contains all externals for a given project (recursively obtained), and in which the user can select which ones to branch, which ones to tag, and which ones to leave pointing to the head revisions. Maybe it is possible to combine tagging and branching in one nice-to-use dialog window because they are so similar. You click on a folder, the dialog window inspects the tree for externals and asks for each external what to do, and then, after selecting the target folder, the process begins.
You're assuming that all users want this to happen. What if my
tagging/branching model is close to, but not quite the same as, what
would be provided by this?
If tools already exist which provide this functionality by integrating
with a "base product" (command-line SVN), why should it be forced into
another "base product" (TSVN).
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-06-16 17:48:13 CEST