We've found that certain files (MS Visual Studio, C++) tend to get
severely modified for some unknown reason when they are maintained by
Visual Studio, such as resource files, projects, and workspaces. In
Visual Source Safe, we can see when someone else has one of these files
checked out, and we go on the honor system of not doing a "multiple"
checkout situation on them, as we have had data loss (possibly because
of VSS's merge tool) in the past when this was not followed. We are in
the process of migrating to Subversion, but have concerns about this
situation. Is there a way to "lock" a file so that someone else won't
edit the file at the same time? The only idea I've had so far would be
to try to set a property on each of those files that would serve as a
kind of "lock". Then prior to someone changing one of those files, they
would check to see what the property was set to to determine if someone
else is currently modifying it or not.
Maybe my fears are unfounded with Subversion handling the merge, as it
could have superior merge abilities in comparison to VSS. I just know
that for some unexplained reason, it appears that occasionally Visual
Studio will "shuffle" these files in such a way that a diff is next to
useless, as everything has been reorganized in a different order. I
don't know what causes this, when it does it, or why. I just know that
it has happened. TIA
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 8 01:17:53 2004