On Fri, May 18, 2012 at 12:53 AM, Thuan Seah Tan <thuan_at_fmod.org> wrote:
>
> I am new to Subversion and currently I am working on Subversion integration
> for the software that I am working on. I have experience with source
> control system such as Perforce, and from what I can tell so far, it seems
> Subversion does not have the equivalent of the checkout for edit that
> systems like Perforce or Team Foundation Server has.
Subversion is like CVS, you can just edit files without marking them
for edit as you have to do in Perforce. That means there's no way for
Subversion to tell if a file has been edited or not until the changes
are committed.
If you want to "broadcast" that you're editing a specific file which
you want exclusive control over (for example, I'm modifying a GIF),
you can "lock" the file before editing it. Then, Subversion will tell
others that you're editing that particular file and don't touch!
Not that locks on Subversion file aren't exclusive. Others can break
your lock (and you'll be warned) to make changes. A "pre-lock" hook
can be created to prevent this type of behavior, but I usually
recommend against this. If a particular developer can't play nicely,
and breaks other people's locks, maybe that developer shouldn't be
working in that environment.
--
David Weintraub
qazwart_at_gmail.com
Received on 2012-05-20 04:12:59 CEST