← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

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

  • Committer: Canonical.com Patch Queue Manager
  • Date: 2010-09-01 08:02:42 UTC
  • mfrom: (5390.3.3 faster-revert-593560)
  • Revision ID: pqm@pqm.ubuntu.com-20100901080242-esg62ody4frwmy66
(spiv) Avoid repeatedly calling self.target.all_file_ids() in
 InterTree.iter_changes. (Andrew Bennetts)

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/user-guide/publishing_a_branch.txt
1
 
.. _publishing_a_branch:
2
 
 
3
1
Publishing a branch
4
2
===================
5
3
 
16
14
store history, not working copies of files, so their enclosing
17
15
repository is usually creating using the ``no-trees`` option, e.g.::
18
16
 
19
 
  bzr init-repo --no-trees bzr+ssh://centralhost/srv/bzr/PROJECT
 
17
  bzr init-repo --no-trees sftp://centralhost/srv/bzr/PROJECT
20
18
 
21
19
You can think of this step as similar to setting up a new cvsroot or
22
20
Subversion repository. However, Bazaar gives you more flexibility
44
42
  bzr add                (populate repository; start version control)
45
43
  bzr commit -m "Initial import"
46
44
                         (publish to central repository)
47
 
  bzr push bzr+ssh://centralhost/srv/bzr/PROJECT/trunk
 
45
  bzr push sftp://centralhost/srv/bzr/PROJECT/trunk
48
46
 
49
47
Here is an example of the second way::
50
48
 
51
49
  bzr init-repo PROJECT  (prepare local repository)
52
50
  cd PROJECT
53
 
  bzr init bzr+ssh://centralhost/srv/bzr/PROJECT/trunk
54
 
  bzr checkout bzr+ssh://centralhost/srv/bzr/PROJECT/trunk
 
51
  bzr init sftp://centralhost/srv/bzr/PROJECT/trunk
 
52
  bzr checkout sftp://centralhost/srv/bzr/PROJECT/trunk
55
53
  cd trunk
56
54
  cp -ar ~/PROJECT .     (copy files in using OS-specific tools)
57
55
  bzr add                (populate repository; start version control)