Compact the description of 'heavyweight checkout' in a single place
converted to 1.6 markup
|Deletions are marked like this.||Additions are marked like this.|
|Line 3:||Line 3:|
|A '''checkout''' is essentially a [:WorkingTree:working tree] that is linked to a branch at a different location.||A '''checkout''' is essentially a [[WorkingTree|working tree]] that is linked to a branch at a different location.|
|Line 9:||Line 9:|
|Checkouts provide a location for people to hack on code and commit. Once a user [:Commit:commit]s, the associated [:Branch:branch] is updated with a new [:Revision:revision] that represents the changes for the commit.||Checkouts provide a location for people to hack on code and commit. Once a user [[Commit|commit]]s, the associated [[Branch|branch]] is updated with a new [[Revision|revision]] that represents the changes for the commit.|
|Line 15:||Line 15:|
| * [:WorkingTree:Working tree]
* [:RepositoryTree:Repository tree]
* [:StandaloneTree:Standalone tree]
| * [[WorkingTree|Working tree]]
* [[RepositoryTree|Repository tree]]
* [[StandaloneTree|Standalone tree]]
A checkout is essentially a working tree that is linked to a branch at a different location.
Checkouts also have local branches, which function as a local cache. This means that checkouts can be used effectively even with branches that are accessed through the Internet. Normal checkouts are sometimes called heavyweight checkouts to distinguish them from lightweight checkouts.
A lightweight checkout is a related construct that lacks the local branch. Lightweight checkouts are smaller, but require fast access to the branch, such as on a LAN or local hard disk.