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

Re: [Subclipse-users] switch and the '--relocate' option

From: Johnathan Gifford <jgifford_at_wernervas.com>
Date: 2006-09-25 20:41:57 CEST

>>> On Mon, Sep 25, 2006 at 1:32 PM, in message
Mark Phippard <markp@softlanding.com> wrote:
> "Johnathan Gifford" <jgifford@wernervas.com> wrote on 09/25/2006
> PM:
>> You know Mark, Georg may have a good point here. As you pointed out
>> my post, if the UUID's of the repository are the same, why could you
>> send a commit to the master server? After all, even making a commit
>> the repository does not 'update' the working copy after the commit.
>> still have to do that manually.
>> This then wouldn't have to involve the Subversion guys would it?
> We cannot just "send a commit". We call the commit API and it is the

> working copy and its location that determine where it goes. I assume
> are not expecting us to run relocate around these commit command?

If the switch process wasn't so intensive, that would be a cool way to
do, wouldn't it!

> Mark
> To unsubscribe, e- mail: users- unsubscribe@subclipse.tigris.org
> For additional commands, e- mail: users- help@subclipse.tigris.org


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Sep 25 20:46:22 2006

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

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