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?
Johnathan
>>> On Mon, Sep 25, 2006 at 1:01 PM, in message
<OFBED545D3.8F4E24C7-ON852571F4.0062F732-852571F4.006305D1@softlanding.com>,
Mark Phippard <markp@softlanding.com> wrote:
> "Georg- W. Koltermann" <Georg.Koltermann@mscsoftware.com> wrote on
> 09/25/2006 02:00:25 PM:
>
>> Mark Phippard schrieb:
>> > ...
>> > You can do a relocate from the SVN Repositories view. This will
> change
>> > the URL for the connection and then run the switch -- relocate on
all
>> > attached working copies.
>> >
>>
>> I'm just going down a similar path, checking out initially from a
>> near- by read- only mirror, then switching to the r/w master server.
>>
>> Over time this gets messy and one wishes it could be automatic.
What do
>> you think about supporting two repository URLs in the plugin, one
for
>> read operations and one for write operations (commit, tag, branch,
>> propset)? That would make everything transparent.
>
> You'd have to ask the Subversion developers for such a feature.
Subclipse
> just runs Subversion API for you. If it cannot do it, Subclipse
cannot do
> 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:30:43 2006