← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/en/user-guide/introducing_bazaar.txt

  • Committer: Andrew Bennetts
  • Date: 2009-12-03 05:57:41 UTC
  • mfrom: (4857 +trunk)
  • mto: This revision was merged to the branch mainline in revision 4869.
  • Revision ID: andrew.bennetts@canonical.com-20091203055741-vmmg0fmjgjw2pwvu
Merge lp:bzr.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/user-guide/introducing_bazaar.txt
18
18
 
19
19
This guide takes you through installing Bazaar and how to use it,
20
20
whether on your own or with a team of other people. If you're already
21
 
familiar with distributed version control and want to dive straight in, 
 
21
familiar with distributed version control and want to dive straight in,
22
22
you may wish to skim this section and jump straight to
23
23
`Learning more`_.
24
24
 
49
49
To record or *commit* these changes, the user needs access to the central
50
50
server and they need to ensure they have merged their work with the latest
51
51
version stored before trying to commit. This approach is known as the
52
 
centralized model. 
 
52
centralized model.
53
53
 
54
54
The centralized model has proven useful over time but it can have some notable
55
55
drawbacks. Firstly, a centralized VCS requires that one is able to connect
87
87
     move them into the core
88
88
 
89
89
 * in companies, easier to work with distributed and outsourced teams.
90
 
   
 
90
 
91
91
For a detailed look at the advantages of distributed VCS tools over
92
92
centralized VCS tools, see http://bazaar-vcs.org/BzrWhy.
93
93