Re: File Locking Question...

The locking mechanism in Subversion is mainly for concurrency. You
lock a file in Subversion if you don't want someone else editing it
and checking it in before you are done with your edits. For example,
if I am updating a logo GIF, I don't want someone else making a change
before I am done because I can't easily merge my changes with their
changes.

However, in Subversion, a lock can be broken by anyone. Think of it
more as a Do Not Disturb sign rather than a lock on a door.

I'm not 100% sure what you are looking for, but it appears you want to
limit access to a particular branch or set of branches while you are
moving them. You may want to take a look at the various pre-commit
triggers that limit write access to particular files or branches.

--
David Weintraub
qazwart_at_gmail.com
On Thu, Nov 6, 2008 at 10:50 AM, BRM <bm_witness_at_yahoo.com> wrote:
> I haven't really tried to use the File Locking feature of SVN before; however, I've run into a situation where I would like to use it and want to clarify that I am understanding the functionality correctly.
>
> I have a branch in my repo that I cut over from CVS (cvs export -> svn import). I am slowly decomposing the branch into a series of separate projects in SVN; however, I have current software that is being released from the cut over branch that depends on the parts I am moving around, and I can't move a particular project until all its dependencies have been moved. Furthermore, many of the projects have overlapping dependencies (e.g. projects A and B both use project C).
>
> As I move a project out of the cut over, I would like to be able to control the edits that go into it - primarily to either sync them with the cutover, or force the updates to it. (I'd rather for the update to it, but that's an internal issue here - not something SVN can resolve easily.) I figured I could use the locking mechanism to achieve this by locking the tree as I moved stuff (using a special checkout for just that purpose) - e.g. move project C to new home, and then lock the old location for project C.
>
> However, I've noticed a failure in checkout, and wanted to ensure that my locking wasn't the cause.
>
> So, to get to the end of all this (aside from suggestions for a better way to do this - all are welcome)...
>
> Locking any part of a tree should not prohibit someone else from updating to (or checking out) the latest checked in revision, correct?
> Even they are checking out from a higher point in the tree, correct?
>
> TIA,
>
> Ben
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org