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

Re: [Fwd: Re: Locking branch has been merged [Re: svn commit: r13571]]

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-03-22 20:38:27 CET

On Mar 22, 2005, at 1:08 PM, Brad Kittenbrink wrote:

> The only way I would imagine it is to not actually put the data there
> until the lock is acquired. For example, store the unlocked file in
> the
> wc as a zero-length read-only stub file or something. When the user
> acquires the lock, copy the contents over from .svn/text-base/ to allow
> read/write access.

But now you're cutting off the nose to spite the face. Lots of files
are un-mergeable... if they're empty files, then they're useless. What
if I need them to build my project? Or run the project? It's no
longer a functional working copy, it's a 'half-copy'. :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 22 20:39:49 2005

This is an archived mail posted to the Subversion Dev mailing list.

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