Re: Repository Issue - Locking error on deleted files

On Tue, Dec 2, 2008 at 5:29 AM, Giulio Troccoli <
Giulio.Troccoli_at_uk.linedata.com> wrote:

> I don't completely agree with you.
>
>
>
> It's true, Subversion uses a different, maybe more modern, approach to
> version control. But since it implements a sort of locking mechanism, then
> it should work correctly.
>
I'm not arguing against the concept of locking. Locks are perfect for file
types that cannot be merged. It prevents someone else from editing a file
while you are working on it. If you can't merge changes, being unable to
lock a file means losing your work when someone beats you to a commit.

However, requiring a lock before deleting doesn't do this. By definition,
deleting a file means you're not making changes to a file that I might have
to merge my changes into. I can always get the file back, so there's no
reason to prevent someone from deleting a file without first locking it. If
I am working on a file that someone else deletes, I can recreate that file,
and put in my changes without worrying about merging.

--
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=978672
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].