... repository¹

The repository is a database containing all files and directories handed over to subversion control. The repository also stores information about changes, log messages, who did what and when, and so on. The user of subversion will never tamper with the repository directly, but rather use a client for all actions he wishes to perform to subversion controlled files.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... copy²

The working copy is whatever was checked out from the repository. Different users have their own working copies, and users may even have several different working copies of a repository.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... files³

This is how RCS works, or sharing of binary file formats as Microsoft Word

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... trunk⁴

The trunk is the main development line in the repository, in contrast to branches that exist in parallel to the main development line.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... revision⁵

In contrast, CVS have revision numbers on every file under control.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... ⁶

This subsection is written for developers without write access to the repository.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... tags⁷

A tag is a marked point in the evolution of the project, an alias for a specific revision of the repository. For humans, it is easier to remember a tag such as release-1.0 than revision number like 1255. Moreover, a conscious choice of tag name makes it easy to remember why revision 1255 was interesting.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.