Version Control System
A situation where an electronic document over its lifetime undergoes a series of changes is quite typical
. In this case, it is often important to have not only the latest version, but several previous ones. In the simplest case, you can easily store multiple versions of the document, numbering them accordingly. But this method is ineffective (you have to keep several nearly identical copies), requires more attention and discipline and often leads to mistakes. Therefore, tools have been developed to automate this work.
Traditional version control systems use a centralized model, where there is a single repository of documents managed by a special server, which handles most of the functions of version control. The user working with documents, must first receive the requested version of a document from the repository, usually creates a local copy of the document, so called. "Working copy". Can be obtained from the latest version or any of the previous ones, which can be selected by a version number or date of creation, and sometimes on other grounds. Once the document made the necessary changes, the new version is placed in storage. Unlike a simple save the file, the previous version is not erased, but also remains in storage and can be obtained there at any time. Server can use the so-called. delta compression - a way of storing documents, which saves only the changes between successive versions, reducing the amount of stored data.
Sometimes a new version runs invisibly to the user (transparent), or an application program that has built in support for such a function, either by using a special file system. In this case, the user simply runs the file, as usual, and when you save a file automatically creates a new version.
It often happens that on one project while working a few people. If two people modify the same file then one of them might accidentally undo the changes made by others. Version control systems keep track of such conflicts and offer a means to address them. Most systems can automatically combine (merge) the changes made by different developers. However, such an automatic merging of changes, usually only available for text files and under the condition that changed different (disjoint) parts of this file. This limitation is due to the fact that most source control systems are intended to support the software development process, and the source code is stored in text files. If the automatic association fails, the system can offer to solve the problem manually.
Often impossible to merge any automatic or manual mode, for example, if the file format is too complicated or, in general, is unknown. Some version control systems make it possible to lock the file in the repository. Blocking does not allow other users to get a working copy or prevent a change of the working copy of the file (for example, means the file system) and provides, therefore, exclusive access only to the user who works with the document.
Many version control systems provide a number of other possibilities:
Allow you to create different versions of a document, so called. branches with a common history of changes to the branch points and with different - after it.
Provide an opportunity to find out who and when added or modified a specific set of lines in the file.
Lead change log, in which users can write notes about what and why they have changed in this version.
Control the access rights of users allowed or denied read or modify data, depending on who is requesting this action.
by: Samson144
Nuvi 3790lmt - It Offers More Than Navigation Features Ethical Inequalities Does Brewii Work Custom lace wigs of your choice Points2shop, A Platform To Be A Next Billionaire What Causes Dark Circles Under the Eyes? 10 000 And: Innovative Gas Fire With Cast Of World-class Brands - Million And, Gas Water Heaters, What Is Rhinoplasty? How to take care of you lace wigs Bbq Pot Roast Prius Hybrid Battery Rebuild - How You Can Fix Your Prius Hybrid Battery Importance of custom lace wigs HTC desire HD deals get the bagful of incentives