Book Image

TortoiseSVN 1.7 Beginner's Guide

By : Lesley Harrison
Book Image

TortoiseSVN 1.7 Beginner's Guide

By: Lesley Harrison

Overview of this book

<p>TortoiseSVN is a Subversion client that gives you quick and easy access to all of Subversion's features. Perhaps you are aware of the importance of version control in software development or document management, but do you know how to use TortoiseSVN for efficient project management? Here is the first book about version control with TortoiseSVN.</p> <p><em>TortoiseSVN 1.7 Beginner's Guide</em> provides a comprehensive coverage of TortoiseSVN in its entirety. It is easy to follow the instructions with clear explanations and screenshots. This book will introduce the important features of TortoiseSVN and at the same time, give you a deeper and clearer understanding of the basic functionality, providing the answers to many questions that are encountered when using TortoiseSVN. TortoiseSVN is a client to SVN, but with this book and TortoiseSVN, you don't need to know anything about SVN, or wade through boring version control theory to get started using one of the most powerful version control applications in the world.</p> <p>The book begins by introducing you to the basics of TortoiseSVN and tools needed to get started with version control. It then dives deep into details, covering the methods available to check and commit changes and keep track of data. Chapters cover conflict management, branching and merging of a project to avoid disturbing the main development version, using TortoiseSVN with popular bug-tracking systems, and much more.</p> <p>By following the practical steps in this book, you will learn every aspect of using TortoiseSVN—from setting up the subversion server, to working with revision logs, and providing security and protection for your subversion server.</p>
Table of Contents (19 chapters)
TortoiseSVN 1.7
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Resolving conflicts


Locking a file is designed to prevent conflicts—if only one person is working on a file, then nothing unexpected can happen.

However, file locking isn't used every time someone wants to work on a file. It doesn't make sense to restrict editing of source code or plain text files in cases where most edits are on unrelated areas of a file, and are unlikely to conflict with each other.

That said, sometimes conflicts do happen, and when they do, you need to be able to resolve them.

This chapter will describe the three main types of file conflict. Conflicts can also arise with branches, and this subject will be discussed in Chapter 5, Branching and Merging.

The most common file conflict is:

  • Local edit/incoming edit

While the most common tree conflicts are:

  • Local edit, incoming delete on update

  • Local delete, incoming edit on update

  • Local delete, incoming delete on update

Scenario 1 – local edit, incoming edit

This kind of file conflict occurs quite frequently if two users try to edit the...