[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVNCopy from within TortoiseSVN

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Mon, 16 Jun 2008 12:51:19 +0100

2008/6/16 tejo dorus <tejodorus_at_hotmail.com>:
>> There is no support for this in the subversion library.
> It is indeed difficult for the subversion library to manage "external"
> objects (it should just manage itself, not the externals). However, the TSVN
> client can act on multiple repositories, and imho, would be a good place for
> this functionality.
>> And it's not
>> clear what it should do with externals anyway when you create a branch
>> or tag.
> As far as I can see, it (TSVN) should do exactly what the svncopy script
> does.

But you haven't said what that is.

> Behaviour for tagging is straightforward: it must tag exactly the
> version number of the current externals head revision.

OK, that sounds sort-of reasonable, although if a particular revision
is not set it means contacting the external's repository to find the
HEAD revision. What happens if the external repo is offline? Should
the operation fail?

> Fro branching, it is
> slightly more complicated, but the key point is that a copy of the externals
> head revision is to be created.

I don't understand this point. You say it is more complicated, but you
don't say what you expect it to do. Are you saying that we also have
to create a branch within the external's repo to match the branch in
the working repo? That will not be the right behaviour in a lot of
cases. For example TSVN uses the Neon and Subversion libraries and we
do not want to create branches of those, and we do not have commit
access to those repos anyway.

>> Externals by definition refer to some external object, so it
>> is likely they would not be changed anyway.
> I do not quite understand this remark. Do you mean that the external
> definitions do not change, or that the underlying external data does not
> change?

The first one.

> The "external definitions" do normally not change, but for tagging, it is
> important that the current head revision number gets included in the
> "externals definition".

Agreed. That has to be done by the user right now. If you relocate
your repository, or if the externals repo is relocated, that is also a
change you have to do manually. SVN support for updating externals is
not very comprehensive.

>> Note that SVN 1.5 will have support for relative external paths, which
>> can be relative to various points:
> This is very ncie feature, which makes life much easier for sharing common
> code. I am very happy with this feature. Imho, if TSVN would, in addition to
> this great new feature, also support branching/tagging with externals, it
> would be extremely powerful. At the moment, not being able to perform easy
> branching/tagging with externals is the only no-go for us to start using
> (T)SVN.


: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
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 13:52:03 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.