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

Re: Tortoise svn - how to chnage target repository

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Fri, 4 Feb 2011 20:34:31 +0000

On 4 February 2011 14:03, Adam Kornicki <srolek2000_at_yahoo.com> wrote:
> I am replying by a browser form so I wasn't aware the text is not quoted.
>
> I guess you misunderstood me - I don't want to recreate a whole repository. What I did (in much simplification) was:
>
> 1. Make a new repository
> 2. Checked out, added and comited a project
> 3. Then decided to change the repository name and structure. Decided it would be easier to just delete it and create a new one.
> 4. I wanted to deply the same WC again on my new repository when the old one was already deleted. That's when I ran into problem

If you want to rename the repository itself, keeping the internal
structure intact:
TSVN->relocate

If you want to re-import an existing working copy into a new
repository, you first have to make it not be a working copy (sorry for
mangled English), then import it and check out again, or do an
in-place import (see the manual to understand how to do this.

> What I want to know is simply how to un-check a folder. Like I wrote before - let's assume I have checked out a wrong folder by mistake (maybe not even a programing folder) and want to un-check it totally from tortoise.

What do you mean by un-check? That's not a term anyone here is
familiar with. If you make up your own terminology you have to expect
people to misunderstand.

> I now only can do it by exporting, deleting and replacing - silly...

But this is a very infrequent operation. Subversion is all about long
term maintenance of a project, not creating one, destroying it and
creating it again. Why would we complicate the user interface by
adding support for something that would almost never be used?

The one place I can agree with you is the way Subversion handles
import, in that an imported folder structure does not become a working
copy, and as described in the subversion manual you have to import and
then checkout - yes, silly. What I describe as import-in-place is a
workaround, but it should really have better support in core
subversion. But again, import is something you do very rarely so there
is little incentive to spend time improving it when there are more
pressing matters to attend to.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2702321
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-02-04 21:34:44 CET

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.