<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Conflict Resolution</title>
<link rel="stylesheet" type="text/css" href="styles.css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1" />
<link rel="home" href="index.html" title="Version Control with Subversion" />
<link rel="up" href="svn.forcvs.html" title="Appendix B. Subversion for CVS Users" />
<link rel="prev" href="svn.forcvs.properties.html" title="Metadata Properties" />
<link rel="next" href="svn.forcvs.binary-and-trans.html" title="Binary Files and Translation" />
</head>
<body>
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Conflict Resolution</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="svn.forcvs.properties.html">Prev</a> </td>
<th width="60%" align="center">Appendix B. Subversion for CVS Users</th>
<td width="20%" align="right"> <a accesskey="n" href="svn.forcvs.binary-and-trans.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" title="Conflict Resolution">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="svn.forcvs.conflicts"></a>Conflict Resolution</h2>
</div>
</div>
</div>
<p>CVS marks conflicts with inline <span class="quote">“<span class="quote">conflict
markers,</span>”</span> and then prints a <code class="literal">C</code> during
an update or merge operation. Historically, this has caused
problems, because CVS isn't doing enough. Many users forget
about (or don't see) the <code class="literal">C</code> after it whizzes
by on their terminal. They often forget that the conflict
markers are even present, and then accidentally commit files
containing those conflict markers.</p>
<p>Subversion solves this problem in a pair of ways. First,
when a conflict occurs in a file, Subversion records the fact
that the file is in a state of conflict, and won't allow you to
commit changes to that file until you explicitly resolve the
conflict. Second, Subversion provides interactive conflict
resolution, which allows you to resolve conflicts as they happen
instead of having to go back and do so after the update or merge
operation completes. See <a class="xref" href="svn.tour.cycle.html#svn.tour.cycle.resolve" title="Resolve Any Conflicts">the section called “Resolve Any Conflicts”</a> for more about conflict resolution in Subversion.</p>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="svn.forcvs.properties.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="svn.forcvs.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="svn.forcvs.binary-and-trans.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Metadata Properties </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> Binary Files and Translation</td>
</tr>
</table>
</div>
<div xmlns="" id="svn-footer">
<hr />
<p>You are reading <em>Version Control with Subversion</em> (for Subversion 1.7), by Ben Collins-Sussman, Brian W. Fitzpatrick, and C. Michael Pilato.<br />
This work is licensed under the <a href="http://creativecommons.org/licenses/by/2.0/">Creative Commons Attribution License v2.0</a>.<br />
To submit comments, corrections, or other contributions to the text, please visit <a href="http://www.svnbook.com/">http://www.svnbook.com/</a>.</p>
</div>
</body>
</html>
distrib
>
Mageia
>
3
>
i586
>
media
>
core-updates
>
by-pkgid
>
1d6e0a3784534d5165fa22faeeca008d
>
files
>
68
