| 33 | Another common version control concept is a tag. A tag is just a “snapshot” of a project in time. In Subversion, this idea already seems to be everywhere. Each repository revision is exactly that—a snapshot of the filesystem after each commit. |
| 34 | |
| 35 | However, people often want to give more human-friendly names to tags, like release-1.0. And they want to make snapshots of smaller subdirectories of the filesystem. After all, it's not so easy to remember that release-1.0 of a piece of software is a particular subdirectory of revision 4822. |
| 36 | * How to create a tag on Linux |
| 37 | {{{ |
| 38 | $ svn copy http://svn.example.com/repos/calc/trunk \ |
| 39 | http://svn.example.com/repos/calc/tags/release-1.0 \ |
| 40 | -m "Tagging the 1.0 release of the 'calc' project." |
| 41 | }}} |
| 42 | Committed revision 351. |
| 43 | |
| 44 | |