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

Re: Roadmap for 1.1 (locking)

From: C.A.T.Magic <c.a.t.magic_at_gmx.at>
Date: 2004-04-02 19:08:10 CEST

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.

    which 'context' does 'the same file' imply
    when talking about locking?
-) is a lock limited to a specific repostory url,
    or does/should it include branches of a file?
-) can a file be 'copied' while locked?
    it probably should, because copying *is* tagging
    and a locked file should still be tag-able.
-) same question for renames,
    property edits, file moves, deletes, etc...
-) 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.


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:08:43 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.