> For the complete documentation index, see [llms.txt](https://raviram.gitbook.io/version-control/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://raviram.gitbook.io/version-control/introduction/what-is-version-control.md).

# What is version control

## What is version control?

What is “version control”, and why should you care? Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later. Using a VCS also generally means that if you screw things up or lose files, you can easily recover. In addition, you get all this for very little overhead.

### Presentation

{% embed url="<https://docs.google.com/presentation/d/1lERdsJY81rFcQsiVt7CkL5ZU-yqD3Jj1lhyH7_7hgvg/edit#slide=id.g92a1ad2113_0_137>" %}

### Local Version Control Systems <a href="#local_version_control_systems" id="local_version_control_systems"></a>

Many people’s version-control method of choice is to copy files into another directory (perhaps a time-stamped directory, if they’re clever). This approach is very common because it is so simple, but it is also incredibly error prone. It is easy to forget which directory you’re in and accidentally write to the wrong file or copy over files you don’t mean to.

To deal with this issue, programmers long ago developed local VCSs that had a **simple database** that kept all the changes to files under revision control.

<figure><img src="https://git-scm.com/book/en/v2/images/local.png" alt=""><figcaption></figcaption></figure>

### Centralized Version Control Systems <a href="#centralized_version_control_systems" id="centralized_version_control_systems"></a>

The next major issue that people encounter is that they need to collaborate with developers on other systems. To deal with this problem, Centralized Version Control Systems (CVCSs) were developed.&#x20;

These systems (such as TFS, CVS, Subversion, and Perforce) have a single server that contains all the versioned files, and a number of clients that check out files from that central place. For many years, this has been the standard for version control.

<figure><img src="https://git-scm.com/book/en/v2/images/centralized.png" alt=""><figcaption></figcaption></figure>

This setup offers many advantages, especially over local VCSs. For example, everyone knows to a certain degree what everyone else on the project is doing. Administrators have fine-grained control over who can do what, and it’s far easier to administer a CVCS than it is to deal with local databases on every client.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://raviram.gitbook.io/version-control/introduction/what-is-version-control.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.