Conflict management in a source version management system

Abstract

To support concurrent development a source version management system must support multiple programmers concurrently accessing shared source code, while maintaining the integrity of the source database. This problem is similar to the problem of concurrency control in database systems, but has a few significant differences. This leads us to view the possible solutions as variations on database transaction management and concurrency control. In particular we consider the possibility of letting transactions interact and managing the conflicts which result.1