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

Re: Feature suggestion: relocation-helper

From: Ulrich Eckhardt <ulrich.eckhardt_at_dominolaser.com>
Date: Mon, 15 Aug 2011 18:12:54 +0200

On Monday 15 August 2011, Rafael M. Heise wrote:
> I'm not sure about what you want. I don't understand exactly what you
> are looking for Ulrich. But I'd like to say how I use to use
> "relocate" and "switch".
> Here where I work we decided to create a new branch for every new
> issue in our product. When we want to release it we merge the branch
> with the trunk and so we compile the project to all our customers.
> Considering that, I normally have only one folder on my disk with the
> current branch I'm working on. When I need to do something in another
> branch, I use the switch command to change my working copy. I use
> switch because I'm not changing the repository location. I'm just
> changing the folder inside the same repository. For example, I change
> my working copy from "branches\A" to "branches\B".

This is understood, and it's not my issue. My issue is only with the relocate
command and not with switching inside the repository.

> But a long time ago, we changed our repository location to a new
> server. In that case I used the relocation command because I was
> changing the URL of the repository. But in this case I don't need to
> see the repo browser or anything else. Actually, as I'm changing the
> repository location, I didn't have any references to that new
> repository, so I can't use the history.
> What I understood with your e-mail is you're changing a lot of working
> copies, and, I guess, you have some reason to keep a lot of working
> copies.

Well, there's a bunch of different projects, all in the same repository, and
I'm more or less involved in all of them. Further, I regularly have an
additional working copy that remains clean and one or two spare ones that are
used for temporary tests etc. This is useful since a checkout takes ten
minutes and a build around thirty minutes, so keeping a few extra WCs saves

> Well, it seems you would like to use the history from your
> first relocation to relocate all another working copies you have. So,
> if I got you correctly, I'd to say that all history refers your
> repository/working copy. And that's why you can't use the history from
> another folder that you change the repository location. Well, in this
> case the history really appears useless, but in my opinion, there is
> nothing more useful to do, because as I said, all history refers your
> repository/working copy.

I'm not 100% sure I understand you, but keep in mind that all my working
copies are from the same repository, so they all must be relocated equally,
see this part of my mail:

> >
> > svn relocate --switch \
> > http://tortoisesvn.tigris.org/svn\
> > https://tortoisesvn.googlecode.com/svn\
> > path/to/WC
> >
> > The path inside the repo that the WC references doesn't matter, you only
> > want to inform the WC that the root of the repo changed location.

Note that this really works and that it doesn't matter where inside the
repository the URL of the working copy points! All that SVN needs is the old
and new URL of the repository _root_. Actually, it doesn't even need the old
root since it knows the old root, which is also what TSVN offers as default.

Maybe I need to give an example....

0. set up svnserve to serve a repo as svn://svn.example.com/svn
1. check out svn://svn.example.com/svn/project-one as wc-one
2. check out svn://svn.example.com/svn/project-two as wc-two
3. check out svn://svn.example.com/svn/project-three as wc-three
4. reconfigure the server to serve the repo as https://svn.example.net
5. relocate wc-one from svn://svn.example.com/svn/project-one to
6. relocate wc-two from svn://svn.example.com/svn/project-two to
7. relocate wc-three from svn://svn.example.com/svn/project-three to

As you see, the three relocations are all from different URLs and to different
URLs, right? And for that, any history in the relocation dialog is useless,
since I can't reuse the former value anyway.

However, and there is the potential for improvement, they could have all
relocated from svn://svn.example.com/svn/ to https://svn.example.net/svn/
instead, and that would have made the history useful! So, to continue the
example, when relocating the first working copy, TSVN should display just the
repository URL (svn://svn.example.com/svn) and not the whole working copy URL
(svn://svn.example.com/svn/project-one) as target path. I would then change
that to the new repository URL (https://svn.example.net/svn). For the second
and third WC, I could then use the exact same repository URL as target URL.

I hope I explained myself clearer now... =|


ML: http://tortoisesvn.tigris.org/list_etiquette.html
FAQ: http://tortoisesvn.net/faq
Domino Laser GmbH, Fangdieckstra�e 75a, 22547 Hamburg, Deutschland
Gesch�ftsf�hrer: Thorsten F�cking, Amtsgericht Hamburg HR B62 932
Visit our website at http://www.dominolaser.com
Diese E-Mail einschlie�lich s�mtlicher Anh�nge ist nur f�r den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empf�nger sein sollten. Die E-Mail ist in diesem Fall zu l�schen und darf weder gelesen, weitergeleitet, ver�ffentlicht oder anderweitig benutzt werden.
E-Mails k�nnen durch Dritte gelesen werden und Viren sowie nichtautorisierte �nderungen enthalten. Domino Laser GmbH ist f�r diese Folgen nicht verantwortlich.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-08-15 18:03:37 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.