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

RE: Re: Roadmap for 1.1 (locking)

From: Stephen Warren <swarren_at_paramanet.com>
Date: 2004-04-02 19:12:30 CEST

> From: C.A.T.Magic [mailto:c.a.t.magic@gmx.at]
> C. Michael Pilato wrote:
> > Locking is intended to prevent collisions between multiple
> > modifications of the same unmergable binary file, not 'svn merge'
> > operations across different ones. "Merge" has too many meanings in
> > VC.
> -) if a file is locked, will 'update' produce a
> local file that has the *readonly flag* set
> so an editor will discover the lock immediatedly?
> .. i've read your locking-plan but found
> no answers to this yet.

Support for working copies that have *all* files read-only, except for files that the user personally owns the lock on, would be nice. That kinda forces users to lock a file to edit it (well, at least hints at it...)

Having this on a per-directory, or per-file would be extremely good.

Having this based on file type (svn:mime-type) would be amazing...

Stephen Warren, Software Engineer, Parama Networks, San Jose, CA
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 2 19:13:23 2004

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.