← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

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

  • Committer: Frank Aspell
  • Date: 2009-02-17 11:40:05 UTC
  • mto: (4054.1.1 doc)
  • mto: This revision was merged to the branch mainline in revision 4056.
  • Revision ID: frankaspell@googlemail.com-20090217114005-ojufrp6rqht664um
Fixed typos.

Fixed some typos in bzr doc's using "aspell -l en -c FILENAME".

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/user-guide/using_gatekeepers.txt
22
22
acceptable, indeed common, to have multiple central branches with
23
23
different gatekeepers, e.g. one branch for the current production
24
24
release and another for the next release. In this case, a task branch
25
 
holding a bug fix will most likely be advertized to both gatekeepers.
 
25
holding a bug fix will most likely be advertised to both gatekeepers.
26
26
 
27
27
One of the great things about this workflow is that it is hugely
28
28
scalable. Large projects can be broken into teams and each