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

RE: encouraging users to switch

From: John Kristian <John.Kristian_at_Siebel.com>
Date: 2005-02-11 19:03:08 CET

Ben Collins-Sussman wrote:
> When I run 'svn up' in my working copy, it *will not* be destroyed.

True. But if my current working directory is elsewhere, unpleasant
things happen. For example, if I change my current working directory to
the parent and execute `svn update foobranch`, it will delete files and
possibly my entire working copy of foobranch. TortoiseSVN has the same
effect. At least, that's what happened when I tried it.

I'm using Windows XP, the svn command line client version 1.1.2 (r12471)
and TortoiseSVN 1.1.2, Build 2205.

- John Kristian

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Thursday, February 10, 2005 8:29 PM
To: John Kristian
Cc: users@subversion.tigris.org
Subject: Re: encouraging users to switch

John Kristian wrote:

> `svn move` is relatively harmful for this use case, because the
> implied `svn delete` causes subsequent updates to do relatively
> harmful things (such as delete working copies, and forget uncommitted
> additions and deletions).

I have to say, I don't understand this whole thread. It sounds like
you're inventing some fantastical problem that just doesn't exist. It
sounds like you're *anticipating* a problem, when it's just no big deal.

Say I have a working copy of /branches/foobranch. Then you come along
and rename the thing to /branches/barbranch.

When I run 'svn up' in my working copy, it *will not* be destroyed. An
update cannot destroy the entire working copy. Instead, I'll get a
semi-cryptic error message about 'unable to replace a directory from
within'. (Yes, it should be a better error message.)

At that point, I email you, or phone you, or turn to my neighbor and ask
what's up. The answer I get back is, "hey, didn't you read the
announcement? The branch moved to 'barbranch'. Just run 'svn switch'
to the new URL." So I do so.

There's no crisis here. No lost work. No need to "enforce" anything at
the server. And honestly, it's not svn's job to send announcements
about things being renamed. All you need to do is set up reasonable
out-of-bounds communication channels in your group. For example,
sending out commit emails that clearly show the rename happening. Or
send an announcement. Regardless, when updates stop working, people
will notice.

Siebel CRM OnDemand. Proven Results for Any Size Company. www.crmondemand.com

This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 11 19:05:42 2005

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

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