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

Re: File lock issue

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: Fri, 2 May 2008 08:14:21 -0500

> -----Original Message-----
> From: Andy Levy [mailto:andy.levy_at_gmail.com]
> Sent: Friday, May 02, 2008 7:06 AM
> To: Srilakshmanan, Lakshman
> Cc: users_at_subversion.tigris.org
> Subject: Re: File lock issue
> > Is there any way of preventing changes across branches till the
> latest copy
> > of the file is merged into the branch before editing or
> is
> > there a way of informing users on different branches that the file
> has been
> > edited and they need to update their copy before proceeding.

In ClearCase, you could prevent a file from being branched. So
unmergeable files would only ever "exist" on the main branch aka, trunk.

Maybe make unmergeable files accessible only via an externals? It's
clumsy since externals can only be defined via a directory.

If SVN symlinks actually resolved to a file/dir (like they do in
ClearCase,) that would be an option also (make a symlink in each branch
to /trunk/.../word.doc, put svn:needs-lock on /trunk/.../word.doc)


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA625

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-02 15:15:15 CEST

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.