《Pragmatic Version Control Using CVS》是The Pragmatic Programmers出版的圖書，作者是Dave Thomas，Andy Hunt
基本介紹
- ISBN：9780974514000
- 作者：Dave Thomas、Andy Hunt
- 出版社：The Pragmatic Programmers
- 出版時間：2003年9月
- 頁數：176
- 定價：USD 29.95
- 裝幀：Paperback
- 叢書：The Pragmatic Starter Kit
內容簡介
This book is a recipe-based approach to using the CVS Version Control system that will get you up and running quickly--and correctly. All projects need version control: it's a foundational piece of any project's infrastructure. Yet half of all project teams in the U.S. don't use any version control at all. Many others don't use it well, and end up experiencing time-consuming pr...(展開全部) This book is a recipe-based approach to using the CVS Version Control system that will get you up and running quickly--and correctly. All projects need version control: it's a foundational piece of any project's infrastructure. Yet half of all project teams in the U.S. don't use any version control at all. Many others don't use it well, and end up experiencing time-consuming problems. Version Control, done well, is your "undo" button for the project: nothing is final, and mistakes are easily rolled back. With version control, you'll never again lose a good idea because someone overwrote your file edits. You can always find out easily who made what changes to the source code--and why. Version control is a project-wide time machine. Dial in a date and see exactly what the entire project looked like yesterday, last Tuesday, or even last year. This book describes a practical, easy-to-follow way of using CVS, the most commonly used version control system in the world (and it's available for free). Instead of presenting the grand Theory of Version Control and describing every possible option (whether you'd ever use it or not), this book focuses on the practical application of CVS. It builds a set of examples of use that parallel the life of typical projects, showing you how to adopt and then enhance your pragmatic use of CVS. With this book, you can: Keep project all assets (not just source code) safe, and never run the risk of losing a great idea; Know how to undo bad decisions--no matter when they were made; Learn how to share code safely, and work in parallel for maxi
