Subversion 1.7英文版完全参考手册

需积分: 7 162 浏览量更新于2024-07-22 收藏 1.85MB PDF 举报

"Subversion 1.7英文版是一份针对Subversion 1.7的完整参考手册，详细地介绍了Subversion的各种操作。Subversion是一个版本控制系统，常用于代码管理，其标签包括svn、subversion、版本控制和代码上传。本书由Ben Collins-Sussman、Brian W. Fitzpatrick和C. Michael Pilato合著，遵循创作共享 Attribution 许可证。" Subversion是一个开源的版本控制系统，用于跟踪和管理文件和目录的变更。在Subversion 1.7版本中，它提供了许多功能和改进，使得团队协作和代码管理更为高效。以下是Subversion的一些核心概念和特点： 1. **版本控制基础**：Subversion的基本思想是维护一个中央仓库（Repository），它是所有版本历史的存储库。用户通常从仓库克隆一份工作副本（Working Copy）到本地，进行编辑和修改。这样，每个开发者都有自己的工作空间，而不会直接对共享资源进行操作。 2. **仓库与工作副本**：仓库是集中式的，存储了所有文件和目录的各个版本。工作副本是仓库的一个本地镜像，用户可以在这个副本上进行日常开发。当用户提交更改时，这些更改会同步回仓库。 3. **版本模型**：Subversion采用分支和合并的版本模型。用户可以创建分支来实验性地开发新特性，而不影响主分支。当准备将这些更改合并回主线时，Subversion提供了工具来解决潜在的冲突。 4. **Subversion组件**：Subversion系统包括客户端工具，如svn命令行客户端，以及服务器端组件，如svnserve或Apache HTTP Server上的mod_dav_svn模块。这些组件共同工作，支持版本控制操作。 5. **新特性**：Subversion 1.7引入了一些新特性，比如优化的工作副本格式，提高了性能和磁盘空间效率。此外，可能还包括增强的冲突解决机制和其他改进。 6. **受众**：Subversion适用于任何需要版本控制的团队，无论是在软件开发、文档编写还是其他任何需要协同编辑和历史追踪的场景。 7. **阅读指南**：书中详细讲解了如何使用Subversion的各种命令和操作，对于初学者和高级用户都有指导价值。 8. **组织结构**：手册通常会从基本概念开始，逐步深入到高级用法，包括创建、更新、提交、分支、合并等操作，以及故障排查和最佳实践。 9. **免费性质**：Subversion和相关的书籍都是免费提供的，这鼓励了广泛使用和社区参与。 10. **致谢**：作者们在书的前言部分通常会感谢那些对项目做出贡献的人，包括测试者、翻译者和代码贡献者。 Subversion 1.7英文版的手册是学习和掌握Subversion系统操作的重要资源，无论你是初学者还是经验丰富的用户，都能从中受益。通过这份详尽的指南，你可以深入了解如何有效地使用Subversion进行版本控制，提升团队协作效率。

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 Subversion name, 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.

While CollabNet started the project, and still funds a large chunk of the work (it pays the salaries of a few full-time Subversion de-

velopers), Subversion is run like most open source projects, governed by a loose, transparent set of rules that encourage merito-

cracy. In 2009, CollabNet worked with the Subversion developers towards the goal of integrating the Subversion project into the

Apache Software Foundation (ASF), one of the most well-known collectives of open source projects in the world. Subversion's

technical roots, community priorities, and development practices were a perfect fit for the ASF, many of whose members were

already active Subversion contributors. In early 2010, Subversion was fully adopted into the ASF's family of top-level projects,

moved its project web presence to http://subversion.apache.org, and was rechristened “Apache Subversion”.

Subversion's Architecture

Figure 1, “Subversion's architecture” illustrates a “mile-high” view of Subversion's design.

Figure 1. Subversion's architecture

Preface

xvi

others of which bypass the network altogether and access the repository directly.

Subversion's Components

Subversion, once installed, has a number of different pieces. The following is a quick overview of what you get. Don't be alarmed

if the brief descriptions leave you scratching your head—plenty more pages in this book are devoted to alleviating that confusion.

svn

The command-line client program

svnversion

A program for reporting the state (in terms of revisions of the items present) of a working copy

svnlook

A tool for directly inspecting a Subversion repository

svnadmin

A tool for creating, tweaking, or repairing a Subversion repository

mod_dav_svn

A plug-in module for the Apache HTTP Server, used to make your repository available to others over a network

svnserve

A custom standalone server program, runnable as a daemon process or invokable by SSH; another way to make your reposit-

ory available to others over a network

svndumpfilter

A program for filtering Subversion repository dump streams

svnsync

A program for incrementally mirroring one repository to another over a network

svnrdump

A program for performing repository history dumps and loads over a network

What's New in Subversion

The first edition of this book was published by O'Reilly Media in 2004, shortly after Subversion had reached 1.0. Since that time,

the Subversion project has continued to release new major releases of the software. Here's a quick summary of major new changes

since Subversion 1.0. Note that this is not a complete list; for full details, please visit Subversion's web site at ht-

tp://subversion.apache.org.

Subversion 1.1 (September 2004)

Release 1.1 introduced FSFS, a flat-file repository storage option for the repository. While the Berkeley DB backend is still

widely used and supported, FSFS has since become the default choice for newly created repositories due to its low barrier to

entry and minimal maintenance requirements. Also in this release came the ability to put symbolic links under version control,

auto-escaping of URLs, and a localized user interface.

Subversion 1.2 (May 2005)

Release 1.2 introduced the ability to create server-side locks on files, thus serializing commit access to certain resources.

While Subversion is still a fundamentally concurrent version control system, certain types of binary files (e.g. art assets) can-

not be merged together. The locking feature fulfills the need to version and protect such resources. With locking also came a

complete WebDAV auto-versioning implementation, allowing Subversion repositories to be mounted as network folders. Fi-

nally, Subversion 1.2 began using a new, faster binary-differencing algorithm to compress and retrieve old versions of files.

Preface

xviii

Subversion 1.3 (December 2005)

Release 1.3 brought path-based authorization controls to the svnserve server, matching a feature formerly found only in the

Apache server. The Apache server, however, gained some new logging features of its own, and Subversion's API bindings to

other languages also made great leaps forward.

Subversion 1.4 (September 2006)

Release 1.4 introduced a whole new tool—svnsync—for doing one-way repository replication over a network. Major parts of

the working copy metadata were revamped to no longer use XML (resulting in client-side speed gains), while the Berkeley DB

repository backend gained the ability to automatically recover itself after a server crash.

Subversion 1.5 (June 2008)

Release 1.5 took much longer to finish than prior releases, but the headliner feature was gigantic: semi-automated tracking of

branching and merging. This was a huge boon for users, and pushed Subversion far beyond the abilities of CVS and into the

ranks of commercial competitors such as Perforce and ClearCase. Subversion 1.5 also introduced a bevy of other user-focused

features, such as interactive resolution of file conflicts, sparse checkouts, client-side management of changelists, powerful new

syntax for externals definitions, and SASL authentication support for the svnserve server.

Subversion 1.6 (March 2009)

Release 1.6 continued to make branching and merging more robust by introducing tree conflicts, and offered improvements to

several other existing features: more interactive conflict resolution options; de-telescoping and outright exclusion support for

sparse checkouts; file-based externals definitions; and operational logging support for svnserve similar to what mod_dav_svn

offered. Also, the command-line client introduced a new shortcut syntax for referring to Subversion repository URLs.

Subversion 1.7 (October 2011)

Release 1.7 was primarily a delivery vehicle for two big plumbing overhauls of existing Subversion components. The largest

and most impactful of these was the so-called “WC-NG”—a complete rewrite of the libsvn_wc working copy management

library. The second change was the introduction of a sleeker HTTP protocol for Subversion client/server interaction. Subver-

sion 1.7 delivered a handful of additional features, many bug fixes, and some notable performance improvements, too.

Audience

This book is written for computer-literate folk who want to use Subversion to manage their data. While Subversion runs on a num-

ber of different operating systems, its primary user interface is command-line-based. That command-line tool (svn), and some ad-

ditional auxiliary programs, are the focus of this book.

For consistency, the examples in this book assume that the reader is using a Unix-like operating system and is relatively comfort-

able with Unix and command-line interfaces. That said, the svn program also runs on non-Unix platforms such as Microsoft Win-

dows. With a few minor exceptions, such as the use of backward slashes (\) instead of forward slashes (/) for path separators, the

input to and output from this tool when run on Windows are identical to that of its Unix counterpart.

Most readers are probably programmers or system administrators who need to track changes to source code. This is the most com-

mon use for Subversion, and therefore it is the scenario underlying all of the book's examples. But Subversion can be used to man-

age changes to any sort of information—images, music, databases, documentation, and so on. To Subversion, all data is just data.

While this book is written with the assumption that the reader has never used a version control system, we've also tried to make it

easy for users of CVS (and other systems) to make a painless leap into Subversion. Special sidebars may mention other version

control systems from time to time, and Appendix B, Subversion for CVS Users summarizes many of the differences between CVS

and Subversion.

Note also that the source code examples used throughout the book are only examples. While they will compile with the proper

compiler incantations, they are intended to illustrate a particular scenario and not necessarily to serve as examples of good pro-

gramming style or practices.

How to Read This Book

Preface

xix

Technical books always face a certain dilemma: whether to cater to top-down or to bottom-up learners. A top-down learner prefers

to read or skim documentation, getting a large overview of how the system works; only then does she actually start using the soft-

ware. A bottom-up learner is a “learn by doing” person—someone who just wants to dive into the software and figure it out as she

goes, referring to book sections when necessary. Most books tend to be written for one type of person or the other, and this book is

undoubtedly biased toward top-down learners. (And if you're actually reading this section, you're probably already a top-down

learner yourself!) However, if you're a bottom-up person, don't despair. While the book may be laid out as a broad survey of Sub-

version topics, the content of each section tends to be heavy with specific examples that you can try-by-doing. For the impatient

folks who just want to get going, you can jump right to Appendix A, Subversion Quick-Start Guide.

Regardless of your learning style, this book aims to be useful to people of widely different backgrounds—from those with no pre-

vious experience in version control to experienced system administrators. Depending on your own background, certain chapters

may be more or less important to you. The following can be considered a “recommended reading list” for various types of readers:

Experienced system administrators

The assumption here is that you've probably used version control before and are dying to get a Subversion server up and run-

ning ASAP. Chapter 5, Repository Administration and Chapter 6, Server Configuration will show you how to create your first

repository and make it available over the network. After that's done, Chapter 2, Basic Usage and Appendix B, Subversion for

CVS Users are the fastest routes to learning the Subversion client.

New users

Your administrator has probably set up Subversion already, and you need to learn how to use the client. If you've never used a

version control system, then Chapter 1, Fundamental Concepts is a vital introduction to the ideas behind version control.

Chapter 2, Basic Usage is a guided tour of the Subversion client.

Advanced users

Whether you're a user or administrator, eventually your project will grow larger. You're going to want to learn how to do more

advanced things with Subversion, such as how to use Subversion's property support (Chapter 3, Advanced Topics), how to use

branches and perform merges (Chapter 4, Branching and Merging), how to configure runtime options (Chapter 7, Customizing

Your Subversion Experience), and other things. These chapters aren't critical at first, but be sure to read them once you're com-

fortable with the basics.

Developers

Presumably, you're already familiar with Subversion, and now want to either extend it or build new software on top of its

many APIs. Chapter 8, Embedding Subversion is just for you.

The book ends with reference material—Chapter 9, Subversion Complete Reference is a reference guide for all Subversion com-

mands, and the appendixes cover a number of useful topics. These are the chapters you're mostly likely to come back to after

you've finished the book.

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.

Preface

剩余467页未读，继续阅读

alex_1990

粉丝: 3
资源: 5

Subversion 1.7英文版完全参考手册

subversion 1.7

subversion1.7

Subversion1.7

CollabNet Subversion 1.7

Version Control with Subversion For Subversion 1.7

SVN手册 For Subversion 1.7

Version Control with Subversion 1.7(r5193)

Subversion 1.7 版本控制指南

Subversion1.7版本控制指南

Subversion 1.7: 管理版本控制的新指南

最新资源