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

Re: how to replicate svn-lock on mirrored repository

From: Ullrich Jans <ullrich.jans_at_elektrobit.com>
Date: Mon, 24 Nov 2014 11:55:11 +0100

Hi,

since nobody took it up, I’ll take a stab at it:

Am 24.11.2014 10:42, schrieb Senthilvelu:
> any help?
>
> On Friday, 21 November 2014 12:16:32 UTC+5:30, Senthilvelu wrote:
>
> I have a mirrored repository which is generated from a source
> repository.
>
> it is getting update regularly. when a user checks out with lock on
> source repo, i want this to be update on the mirror repo, which is
> not happening using svnsync.
>
> is there anyway i can update the lock as well on the mirror repo
>
> thanks senthil

Usually, you shouldn’t need to exert any special effort to forward locks
to the mirror. The property svn:needs-lock is a normal property, so it
gets synced out to the mirror with the normal procedure.

When a client tries to get a lock on a file, it always asks the master,
when someone else has the lock, the client will get told even without
the mirror having to do anything.

So, there is no reason for the mirror to know.

Does this help?

Ulli

-- 
Ullrich Jans, Specialist, IT-A
Phone: +49 9131 7701-6627, mailto:ullrich.jans_at_elektrobit.com
Fax: +49 9131 7701-6333, www.elektrobit.com
Elektrobit Automotive GmbH, Am Wolfsmantel 46, 91058 Erlangen, Germany
Managing Directors: Alexander Kocher, Gregor Zink
Register Court Fürth HRB 4886
----------------------------------------------------------------
Please note: This e-mail may contain confidential information
intended solely for the addressee. If you have received this
e-mail in error, please do not disclose it to anyone, notify
the sender promptly, and delete the message from your system.
Thank you.
Received on 2014-11-24 12:00:04 CET

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.