
794
|
Chapter 12: Source Code Management: An Overview
This is the Title of the Book, eMatter Edition
Copyright © 2006 O’Reilly & Associates, Inc. All rights reserved.
development. In our hypothetical example, all the bugs fixed in whizprog 1.0
to create version 1.1 should also be fixed in the ongoing 2.0 development.
Source code management systems can help you automate the process of
merging.
Conflict
A conflict occurs when two developers make inconsistent changes to the same
part of a source file. Modern source code management systems detect the
conflict, usually marking the conflicting parts of the file in your working copy
using special markers. You first discuss the conflict with the other developer,
in order to arrive at a correct resolution of the conflict. Once that’s done, you
then resolve the conflict manually (by making the appropriate changes) and
check in the new version of the file.
Client/Server
As with other “client/server” networking models, the idea here is that the
repository is stored on one machine, the server, and that different developers
may access the repository from multiple client systems. This powerful feature
facilitates distributed development, allowing developers to work easily on
their local systems, with the repository kept in a central place where it can be
easily accessed and administered.
Usage Models
Different systems have different conceptual “models” as to how they’re ...