Subversion 1.6 版本控制指南

Subversion

需积分: 4 179 浏览量更新于2024-08-01 收藏 1.56MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"Version Control with Subversion" 是一本关于Subversion 1.6版本控制系统的详细指南，由Ben Collins-Sussman、Brian W. Fitzpatrick和C. Michael Pilato共同编写。这本书的内容基于修订版r3586，并且计划在某个待定日期发布。本书的版权属于作者，遵循创作共用署名许可，允许自由传播和使用，但需给予作者适当的署名权。更多关于许可的信息，可以访问Creative Commons的官方网站或向其邮寄查询。书的内容涵盖了Subversion的基础知识到深入的使用技巧，旨在帮助读者理解和掌握这个版本控制系统。书中的章节包括但不限于： 1. 前言（Foreword）：通常由与作品相关的专家或作者的朋友撰写，介绍本书的背景和价值。 2. 序言（Preface）：作者阐述了本书的写作目的、受众定位、阅读方法以及书中使用的约定和符号。 3. 受众定位（Audience）：明确了本书主要面向哪些读者群体，可能是开发人员、项目管理者或其他需要使用版本控制的人群。 4. 如何阅读本书（How to Read This Book）：指导读者如何有效利用书中的信息。 5. 本书的约定（Conventions Used in This Book）：解释了书中使用的特定排版和符号规则。 6. 本书的组织结构（Organization of This Book）：简述各章节的主题和内容布局。 7. 这本书是免费的（This Book Is Free）：强调了本书的开放许可政策，允许读者免费获取和使用。 8. 致谢（Acknowledgments）：作者对在创作过程中提供帮助和支持的人表示感谢。 9. 三位作者各自的致谢词：Ben Collins-Sussman、Brian W. Fitzpatrick和C. Michael Pilato分别表达了对合作者、支持者和社区的感激之情。 10. 什么是Subversion？（What Is Subversion?）：介绍了Subversion的基本概念和功能，包括它作为版本控制系统的核心作用。 11. Subversion是否适合你？（Is Subversion the Right Tool?）：帮助读者判断Subversion是否符合他们的需求。 12. Subversion的历史（Subversion's History）：回顾Subversion的发展历程和重大事件。 13. Subversion的架构（Subversion's Architecture）：深入解析Subversion的设计原理和内部工作机制。 14. Subversion的组件（Subversion's Components）：介绍Subversion系统的主要组成部分及其相互作用。 15. Subversion的新特性（What's New in Subversion）：列出Subversion 1.6相较于早期版本的重要改进和新功能。书的其余部分可能会详细介绍如何安装和配置Subversion，使用基本命令行工具，管理项目，处理分支和合并，以及与其他工具和系统的集成。此外，还可能包含解决常见问题、最佳实践和高级主题，如访问控制、备份策略和故障排查等内容。通过本书，读者不仅可以学习到Subversion的基本操作，还能了解到如何在实际项目中有效利用版本控制，提高团队协作效率，保障代码的安全和质量。对于任何想要掌握Subversion的个人或团队来说，这是一份宝贵的资源。

资源详情

资源推荐

This icon designates a warning. Pay close attention to these to avoid running into problems.

Organization of This Book

The chapters that follow and their contents are listed here:

Chapter 1, Fundamental Concepts

Explains the basics of version control and different versioning models, along with Subversion's repository, working copies,

and revisions.

Chapter 2, Basic Usage

Walks you through a day in the life of a Subversion user. It demonstrates how to use a Subversion client to obtain, modify, and

commit data.

Chapter 3, Advanced Topics

Covers more complex features that regular users will eventually come into contact with, such as versioned metadata, file lock-

ing, and peg revisions.

Chapter 4, Branching and Merging

Discusses branches, merges, and tagging, including best practices for branching and merging, common use cases, how to undo

changes, and how to easily swing from one branch to the next.

Chapter 5, Repository Administration

Describes the basics of the Subversion repository, how to create, configure, and maintain a repository, and the tools you can

use to do all of this.

Chapter 6, Server Configuration

Explains how to configure your Subversion server and offers different ways to access your repository: HTTP, the svn pro-

tocol, and local disk access. It also covers the details of authentication, authorization and anonymous access.

Chapter 7, Customizing Your Subversion Experience

Explores the Subversion client configuration files, the handling of internationalized text, and how to make external tools co-

operate with Subversion.

Chapter 8, Embedding Subversion

Describes the internals of Subversion, the Subversion filesystem, and the working copy administrative areas from a program-

mer's point of view. It also demonstrates how to use the public APIs to write a program that uses Subversion.

Chapter 9, Subversion Complete Reference

Explains in great detail every subcommand of svn, svnadmin, and svnlook with plenty of examples for the whole family!

Appendix A, Subversion Quick-Start Guide

For the impatient, a whirlwind explanation of how to install Subversion and start using it immediately. You have been warned.

Appendix B, Subversion for CVS Users

Covers the similarities and differences between Subversion and CVS, with numerous suggestions on how to break all the bad

habits you picked up from years of using CVS. Included are descriptions of Subversion revision numbers, versioned director-

ies, offline operations, update versus status, branches, tags, metadata, conflict resolution, and authentication.

Appendix C, WebDAV and Autoversioning

Describes the details of WebDAV and DeltaV and how you can configure your Subversion repository to be mounted read/

write as a DAV share.

Appendix D, Copyright

A copy of the Creative Commons Attribution License, under which this book is licensed.

Preface

xvi

Oh, and thanks, Karl, for being too overworked to write this book yourself.

This Book Is Free

This book started out as bits of documentation written by Subversion project developers, which were then coalesced into a single

work and rewritten. As such, it has always been under a free license (see Appendix D, Copyright). In fact, the book was written in

the public eye, originally as part of the Subversion project itself. This means two things:

• You will always find the latest version of this book in the book's own Subversion repository.

• You can make changes to this book and redistribute it however you wish—it's under a free license. Your only obligation is to

maintain proper attribution to the original authors. Of course, we'd much rather you send feedback and patches to the Subversion

developer community, instead of distributing your private version of this book.

The online home of this book's development and most of the volunteer-driven translation efforts regarding it is ht-

tp://svnbook.red-bean.com. There you can find links to the latest releases and tagged versions of the book in various formats, as

well as instructions for accessing the book's Subversion repository (where its DocBook XML source code lives). Feedback is wel-

comed—encouraged, even. Please submit all comments, complaints, and patches against the book sources to

<svnbook-dev@red-bean.com>.

Acknowledgments

This book would not be possible (nor very useful) if Subversion did not exist. For that, the authors would like to thank Brian

Behlendorf and CollabNet for the vision to fund such a risky and ambitious new open source project; Jim Blandy for the original

Subversion name and design—we love you, Jim; and Karl Fogel for being such a good friend and a great community leader, in that

order.

Thanks to O'Reilly and our various editors: Chuck Toporek, Linda Mui, Tatiana Apandi, Mary Brady, and Mary Treseler. Their pa-

tience and support has been tremendous.

Finally, we thank the countless people who contributed to this book with informal reviews, suggestions, and patches. While this is

undoubtedly not a complete list, this book would be incomplete and incorrect without their help: Bhuvaneswaran A, David Alber,

C. Scott Ananian, David Anderson, Ariel Arjona, Seth Arnold, Jani Averbach, Charles Bailey, Ryan Barrett, Francois Beausoleil,

Brian R. Becker, Yves Bergeron, Karl Berry, Jennifer Bevan, Matt Blais, Jim Blandy, Phil Bordelon, Sietse Brouwer, Tom Brown,

Zack Brown, Martin Buchholz, Paul Burba, Sean Callan-Hinsvark, Branko Cibej, Archie Cobbs, Jason Cohen, Ryan Cresawn,

John R. Daily, Peter Davis, Olivier Davy, Robert P. J. Day, Mo DeJong, Brian Denny, Joe Drew, Markus Dreyer, Nick Duffek,

Boris Dusek, Ben Elliston, Justin Erenkrantz, Jens M. Felderhoff, Kyle Ferrio, Shlomi Fish, Julian Foad, Chris Foote, Martin Fur-

ter, Vlad Georgescu, Peter Gervai, Dave Gilbert, Eric Gillespie, David Glasser, Marcel Gosselin, Lieven Govaerts, Steve Green-

land, Matthew Gregan, Tom Gregory, Maverick Grey, Art Haas, Mark E. Hamilton, Eric Hanchrow, Liam Healy, Malte Helmert,

Michael Henderson, Øyvind A. Holm, Greg Hudson, Alexis Huxley, Auke Jilderda, Toby Johnson, Jens B. Jorgensen, Tez Kami-

hira, David Kimdon, Mark Benedetto King, Robert Kleemann, Erik Kline, Josh Knowles, Andreas J. Koenig, Axel Kollmorgen,

Nuutti Kotivuori, Kalin Kozhuharov, Matt Kraai, Regis Kuckaertz, Stefan Kueng, Steve Kunkee, Scott Lamb, Wesley J. Landaker,

Benjamin Landsteiner, Vincent Lefevre, Morten Ludvigsen, Dennis Lundberg, Paul Lussier, Bruce A. Mah, Jonathon Mah, Karl

Heinz Marbaise, Philip Martin, Feliciano Matias, Neil Mayhew, Patrick Mayweg, Gareth McCaughan, Craig McElroy, Simon

McKenna, Christophe Meresse, Jonathan Metillon, Jean-Francois Michaud, Jon Middleton, Robert Moerland, Marcel Molina Jr.,

Tim Moloney, Alexander Mueller, Tabish Mustufa, Christopher Ness, Roman Neuhauser, Mats Nilsson, Greg Noel, Joe Orton,

Eric Paire, Dimitri Papadopoulos-Orfanos, Jerry Peek, Chris Pepper, Amy Lyn Pilato, Kevin Pilch-Bisson, Hans Polak, Dmitriy

Popkov, Michael Price, Mark Proctor, Steffen Prohaska, Daniel Rall, Srinivasa Ramanujan, Jack Repenning, Tobias Ringstrom,

Jason Robbins, Garrett Rooney, Joel Rosdahl, Christian Sauer, Ryan Schmidt, Jochem Schulenklopper, Jens Seidel, Daniel Shahaf,

Larry Shatzer, Danil Shopyrin, Erik Sjoelund, Joey Smith, W. Snyder, Stefan Sperling, Robert Spier, M. S. Sriram, Russell

Steicke, David Steinbrunner, Sander Striker, David Summers, Johan Sundstroem, Ed Swierk, John Szakmeister, Arfrever Frehtes

Taifersar Arahesis, Robert Tasarz, Michael W. Thelen, Mason Thomas, Erik van der Kolk, Joshua Varner, Eric Wadsworth, Chris

Wagner, Colin Watson, Alex Waugh, Chad Whitacre, Andy Whitcroft, Josef Wolf, Luke Worth, Hyrum Wright, Blair Zajac, Flori-

an Zumbiehl, and the entire Subversion community.

Preface

xvii

From Ben Collins-Sussman

Thanks to my wife Frances, who, for many months, got to hear “But honey, I'm still working on the book,” rather than the usual

“But honey, I'm still doing email.” I don't know where she gets all that patience! She's my perfect counterbalance.

Thanks to my extended family and friends for their sincere encouragement, despite having no actual interest in the subject. (You

know, the ones who say, “Ooh, you wrote a book?” and then when you tell them it's a computer book, sort of glaze over.)

Thanks to all my close friends, who make me a rich, rich man. Don't look at me that way—you know who you are.

Thanks to my parents for the perfect low-level formatting and being unbelievable role models. Thanks to my kids for the opportun-

ity to pass that on.

From Brian W. Fitzpatrick

Huge thanks to my wife Marie for being incredibly understanding, supportive, and most of all, patient. Thank you to my brother

Eric who first introduced me to Unix programming way back when. Thanks to my Mom and Grandmother for all their support, not

to mention enduring a Christmas holiday where I came home and promptly buried my head in my laptop to work on the book.

To Mike and Ben: it was a pleasure working with you on the book. Heck, it's a pleasure working with you at work!

To everyone in the Subversion community and the Apache Software Foundation, thanks for having me. Not a day goes by where I

don't learn something from at least one of you.

Lastly, thanks to my grandfather, who always told me that “freedom equals responsibility.” I couldn't agree more.

From C. Michael Pilato

Special thanks to Amy, my best friend and wife of more than ten incredible years, for her love and patient support, for putting up

with the late nights, and for graciously enduring the version control processes I've imposed on her. Don't worry, sweetheart—you'll

be a TortoiseSVN wizard in no time!

Gavin, you're able to read half of the words in this book yourself now; sadly, it's the other half that provide the key concepts. And

sorry, Aidan—I couldn't find a way to work Disney/Pixar characters into the text. But Daddy loves you both, and can't wait to

teach you about programming.

Mom and Dad, thanks for your constant support and enthusiasm. Mom- and Dad-in-law, thanks for all of the same plus your fab-

ulous daughter.

Hats off to Shep Kendall, through whom the world of computers was first opened to me; Ben Collins-Sussman, my tour guide

through the open source world; Karl Fogel, you are my .emacs; Greg Stein, for oozing practical programming know-how; and

Brian Fitzpatrick, for sharing this writing experience with me. To the many folks from whom I am constantly picking up new

knowledge—keep dropping it!

Finally, to the One who perfectly demonstrates creative excellence—thank You.

What Is Subversion?

Subversion is a free/open source version control system. That is, Subversion manages files and directories, and the changes made

to them, over time. This allows you to recover older versions of your data or examine the history of how your data changed. In this

regard, many people think of a version control system as a sort of “time machine.”

Subversion can operate across networks, which allows it to be used by people on different computers. At some level, the ability for

various people to modify and manage the same set of data from their respective locations fosters collaboration. Progress can occur

more quickly without a single conduit through which all modifications must occur. And because the work is versioned, you need

not fear that quality is the trade-off for losing that conduit—if some incorrect change is made to the data, just undo that change.

Preface

xviii

Or as a friend puts it, “swatting a fly with a Buick.”

Some version control systems are also software configuration management (SCM) systems. These systems are specifically tailored

to manage trees of source code and have many features that are specific to software development—such as natively understanding

programming languages, or supplying tools for building software. Subversion, however, is not one of these systems. It is a general

system that can be used to manage any collection of files. For you, those files might be source code—for others, anything from

grocery shopping lists to digital video mixdowns and beyond.

Is Subversion the Right Tool?

If you're a user or system administrator pondering the use of Subversion, the first question you should ask yourself is: "Is this the

right tool for the job?" Subversion is a fantastic hammer, but be careful not to view every problem as a nail.

If you need to archive old versions of files and directories, possibly resurrect them, or examine logs of how they've changed over

time, then Subversion is exactly the right tool for you. If you need to collaborate with people on documents (usually over a net-

work) and keep track of who made which changes, then Subversion is also appropriate. This is why Subversion is so often used in

software development environments—working on a development team is an inherently social activity, and Subversion makes it

easy to collaborate with other programmers. Of course, there's a cost to using Subversion as well: administrative overhead. You'll

need to manage a data repository to store the information and all its history, and be diligent about backing it up. When working

with the data on a daily basis, you won't be able to copy, move, rename, or delete files the way you usually do. Instead, you'll have

to do all of those things through Subversion.

Assuming you're fine with the extra workflow, you should still make sure you're not using Subversion to solve a problem that other

tools solve better. For example, because Subversion replicates data to all the collaborators involved, a common misuse is to treat it

as a generic distribution system. People will sometimes use Subversion to distribute huge collections of photos, digital music, or

software packages. The problem is that this sort of data usually isn't changing at all. The collection itself grows over time, but the

individual files within the collection aren't being changed. In this case, using Subversion is “overkill.”

There are simpler tools that

efficiently replicate data without the overhead of tracking changes, such as rsync or unison.

Subversion's History

In early 2000, CollabNet, Inc. (http://www.collab.net) began seeking developers to write a replacement for CVS. CollabNet offers

a collaboration software suite called CollabNet Enterprise Edition (CEE), of which one component is version control. Although

CEE used CVS as its initial version control system, CVS's limitations were obvious from the beginning, and CollabNet knew it

would eventually have to find something better. Unfortunately, CVS had become the de facto standard in the open source world

largely because there wasn't anything better, at least not under a free license. So CollabNet determined to write a new version con-

trol system from scratch, retaining the basic ideas of CVS, but without the bugs and misfeatures.

In February 2000, they contacted Karl Fogel, the author of Open Source Development with CVS (Coriolis, 1999), and asked if he'd

like to work on this new project. Coincidentally, at the time Karl was already discussing a design for a new version control system

with his friend Jim Blandy. In 1995, the two had started Cyclic Software, a company providing CVS support contracts, and al-

though they later sold the business, they still used CVS every day at their jobs. Their frustration with CVS had led Jim to think

carefully about better ways to manage versioned data, and he'd already come up with not only the name “Subversion,” but also the

basic design of the Subversion data store. When CollabNet called, Karl immediately agreed to work on the project, and Jim got his

employer, Red Hat Software, to essentially donate him to the project for an indefinite period of time. CollabNet hired Karl and Ben

Collins-Sussman, and detailed design work began in May 2000. With the help of some well-placed prods from Brian Behlendorf

and Jason Robbins of CollabNet, and from Greg Stein (at the time an independent developer active in the WebDAV/DeltaV spe-

cification process), Subversion quickly attracted a community of active developers. It turned out that many people had encountered

the same frustrating experiences with CVS and welcomed the chance to finally do something about it.

The original design team settled on some simple goals. They didn't want to break new ground in version control methodology, they

just wanted to fix CVS. They decided that Subversion would match CVS's features and preserve the same development model, but

not duplicate CVS's most obvious flaws. And although it did not need to be a drop-in replacement for CVS, it should be similar

enough that any CVS user could make the switch with little effort.

After 14 months of coding, Subversion became “self-hosting” on August 31, 2001. That is, Subversion developers stopped using

CVS to manage Subversion's own source code and started using Subversion instead.

Preface

xix

剩余396页未读，继续阅读

daadai1

粉丝: 1
资源: 1

Subversion 1.6 版本控制指南

Version Control with Subversion （svn手册中英文版）

Version Control with Subversion_en

Version Control System的基本原理与实践

mac的idea使用svn

idea怎么配置subversion管理

pycharm cannot run svn

idea Can't use Subversion command line client: svn The path to the Subversion executable is probably wrong.

idea配置svn地址

linux中查看vcs版本

idea 整合svn

idea使用svn导入项目

svn拉取springmvc项目

subversion-1.14.2 文件夹怎么安装到Ubuntu

android studio 中如何将仓库由subversion换为git

qtcreate 5.5

intellij idea配置svn

linux安装subversion

subversion-1.14.2 文件夹怎么安装ubuntu

Cannot run program "svn" (in directory "D:\work\20230905-bj-blkg-v663"): CreateProcess error=2, 系统找不到指定的文件

idea中svn安装

最新资源