RE: which version control supports file locking and who has it locked

> From: Doug Robinson [mailto:doug.robinson_at_wandisco.com]
> Sent: Monday, June 13, 2016 4:49 PM
> To: Johan Corveleyn
> Cc: Mark McKeown; Andreas Stieger; users_at_subversion.apache.org
> Subject: Re: which version control supports file locking and who has it locked
>
>
> I'm not sure about Perforce's implementation.  However, just for
> comparison: with ClearCase Dynamic Views you can *not* edit the file
> without a checkout.  The Dynamic View implementation is via an actual
> OS file system so you can't beat it.  And everyone can see that checkout.

What about eclipsed files?

And never forget that Someone can always copy the file out of the view/workspace to make changes to it because they're in a rush to leave for vacation. Of course such a person, after coming back from vacation, would *never* copy their week old modified file back in to the workspace/view in order to check in their changes after the lock is released thus undoing the previous week's work of commits.

Point is, you can't completely idiot proof anything because there's always one idiot who's smarter than you.
Received on 2016-06-14 19:10:38 CEST