Bazaar

Bazaar

 




Wiki Tools

  • Find Page
  • Recent Changes
  • Page History
  • Attachments

Differences between revisions 6 and 7
Revision 6 as of 2008-04-16 00:18:57
Size: 1030
Editor: AaronBentley
Comment:
Revision 7 as of 2009-03-15 13:21:19
Size: 1017
Comment: Compact the description of 'heavyweight checkout' in a single place
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Checkouts also have local branches, which function as a local cache. This means that heavyweight checkouts can be used effectively even with branches that are accessed through the Internet. 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.
Line 7: Line 7:
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. 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.

Checkout

A checkout is essentially a [:WorkingTree: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.

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.

See also

  • CheckoutTutorial

  • [:WorkingTree:Working tree]

  • [:RepositoryTree:Repository tree]

  • [:StandaloneTree:Standalone tree]


CategoryTerm