>>> On Mon, Sep 25, 2006 at 1:32 PM, in message
<OF94D43F94.22B8C966-ON852571F4.0065BC4C-852571F4.0065D378@softlanding.com>,
Mark Phippard <markp@softlanding.com> wrote:
> "Johnathan Gifford" <jgifford@wernervas.com> wrote on 09/25/2006
02:29:46
> PM:
>
>> You know Mark, Georg may have a good point here. As you pointed out
in
>> my post, if the UUID's of the repository are the same, why could you
not
>> send a commit to the master server? After all, even making a commit
to
>> the repository does not 'update' the working copy after the commit.
You
>> 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
you
> 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
Johnathan
---------------------------------------------------------------------
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