SVN's understanding of repository, working directory

The server environment is basically well, ready to start the project environment, the successor project will enter the model of team development, must have a version of the management tools. And for version management tools, I do not know much, before just used SVN, then svn it. Don't say much nonsense, get to the point.

Anyone who has known SVN knows that SVN is divided into server and client. The server primarily records and maintains all client operations on the repository, and the client is used by each developer to develop their own standalone version. The process of building an SVN server is not difficult. Degree Niang or Google, it is easy to find relevant information, so this article will not be redundant. This article is not about documenting how to build an SVN server, but about the basic concepts and commands of the SVN service side.

After the server has been installed with Subversion (SVN server), the SVN servers need to have a repository first, and the repository is created with the svnadmin Create Path command (for example, the repository I created Svnadmin create/home/ Svn/pro), this repository contains some of the information that SVN uses for versioning, directory locks, hooks, directories that have been added to version control in the repository (the following writing managed directories) and files, basic configuration information, and so on. Conf directory, contains the user, permissions and other configuration information files. Here do not do a detailed analysis, want to know a friend, you can go to Google under the configuration of various configuration files, generally have a detailed description of the configuration file.

Once the repository is set up, the repository is a clean repository. To incorporate a directory into version management, you also need to import the data into the repository via the SVN import command. Suppose you need to incorporate directory/home/staff/project into the repository control, using the command directly (SVN import/home/staff/project file:///home/svn/pro-m "Initialize import" To I just started to build the SVN server, SVN import this command let me confused for a long time. What exactly did svn import do? Here we need to explain the functionality of the SVN repository, which contains only the configuration information and management information of the managed directory, as explained earlier in this article, not just storing the data directly in the repository. Therefore, the "managed Directory" (/home/staff/project) is included in the repository Operation SVN import, first, the repository adds some management information for the managed directory. The second is to add a version control letter in the "managed directory", under the same level directory of/home/staff/project, a. Subversion directory will be generated, and the incremental or decrement information of some of the files modified by the client will be stored in this. Subversion directory. And the repository is only for version number, user, lock and other basic management.

As for the developer's working directory, it is a working copy of the managed directory, and different developers have a working directory of their own. Concurrent development of projects through client-side update, Commit, and so on. Unknowingly, nagging so much, using SVN or other version management tools of friends, should be able to understand it. Because, it's not too cumbersome.

I build SVN environment, for it does not understand, led to spend a lot of time, looked up a lot of information just understand, take advantage of now still remember, here record down, convenient later consult. I have limited knowledge, if there is any misunderstanding of the place, welcome to correct, thank you!

SVN's understanding of repository, working directory