| |||||||||||||
VCS with locksVCS with locksPosted Feb 27, 2010 18:46 UTC (Sat) by nix (subscriber, #2304)In reply to: VCS with locks by man_ls Parent article: Hg Init: a Mercurial tutorial
I've worked at places where auditors who believed this came in, and tried
to force everyone to go back from git to (I kid you not) SCCS.
Convincing them otherwise was most unpleasant. I wish we could just have
(Log in to post comments)
VCS with locks Posted Feb 27, 2010 21:17 UTC (Sat) by man_ls (subscriber, #15091) [Link] You were quite brave to convince the auditors. In a way it is easy since git provides many more auditing features, but the process does not look so rosy.But I have also to say that you were lucky: I have worked at places where the developers themselves could not be convinced to work without locks, and distributed VCS was alien technology. It was trebly painful: they did not trust nor understand lock-free VCS, they should have known better, and up to now they are still working with locks (with all that it entails).
VCS with locks Posted Feb 27, 2010 22:03 UTC (Sat) by nix (subscriber, #2304) [Link]
It helped that other branches of the same organization (for 'other
branches' read 'sitting across the room') had been convinced by these auditors, so were using SCCS with a horrible shell script wrapper to attempt to provide some semblance of branching, and auditor-imposed constraints to prevent reservation in a wide variety of situations (such as a single client out of hundreds querying something in *any* previous change touching the same file: want to make an unrelated change touching such a file, got to find a way to make it in a different file instead!), so everyone talking to the auditors knew *exactly* how horrible their proposed golden age would be.
|
|||||||||||||