SVN use experience Three

21, all the development code stored on the trunk.

Common Branch Mode:

A, publishing branch: In the code development to a certain stage, the establishment of the release branch, the current version out, copied to the branches directory, for a full rigorous testing, such as the discovery of bugs in the current version of the repair, and synchronized update trunk bug, after the test completed, Copy the files to the tags directory and submit them to the customer.

b, characteristics of the branch: if you need to make complex changes, will affect the stability of the trunk code, it is recommended to establish a feature branch, and other features stable, and then the truck backbone merge

22, Tag tag: It is a project, a snapshot of a time, this term is very common, each submission of a revised version is actually a precise snapshot.

<?xml:namespace prefix = o ns = "Urn:schemas-microsoft-com:office:office"/>

23, the classic common version of the library layout:

If it is a single item, it is recommended that you use the following format

/trunk keep the main line of project development.

/branches saves the various development branches of the project.

/tags saves the item's label, which is a branch that will never be modified after it is created, such as releasing a release version.

If multiple items are in the same version library, it is recommended that you use the following format

/rigtms/trunk

/rigtms/branches

/rigtms/tags

/docprotect/trunk

/docprotect/branches

/docprotect/tags

Comments * * Personal comparison tends to use the first way, one is simple format, the end user is not easy to cause confusion, the second is the version of the library permissions control is relatively simple, three is a later backup/restore relatively easy line

24, SVN data storage format has Berkeley DB and Fsfs. The version we are using now defaults to the FSFS format data store.

25, SVN self-with tools

(You can use these tools to enter Svnadmin Help, Svnlook, and so on in command line mode)

Svnadmin: Provides the ability to create SVN version libraries and can also be used to maintain these versions of libraries.

Svnlook: Used to view different revisions and things in the version library (it does not change the content of the version).

Svndumpfilter: Can be simply and quickly used as a path-based filter for SVN version library history.

Svnsync: Transfer The history of one version library to another. The feature is that remote operations (source, target, and SVNSYSNC programs can be used on different computers.) ）

26, SVN save disk space, the main methods:

1, the use of incremental technology, two sets of data, only one of the records, the other group is only stored with the first group of different parts.

2, due to client and server network anomalies, or client SVN process abort abnormally, can cause file commit transactions failed, you may delete the transaction aborted unexpectedly. You can use $svnadmin Lstxns myrepos to clear it.

27. Delete Berkeley DB log files that are not used

Svnadmin List–unused–dblogs/path/to/repos

Rm ' Svnadmin list–unused-dblogs/path/to/repos '