/brz/remove-bazaar

To get this branch, use:
bzr branch http://gegoxaren.bato24.eu/bzr/brz/remove-bazaar

« back to all changes in this revision

Viewing changes to doc/en/admin-guide/simple-setups.txt

  • Committer: Jelmer Vernooij
  • Date: 2019-05-29 03:22:34 UTC
  • mfrom: (7303 work)
  • mto: This revision was merged to the branch mainline in revision 7306.
  • Revision ID: jelmer@jelmer.uk-20190529032234-mt3fuws8gq03tapi
Merge trunk.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/admin-guide/simple-setups.txt
37
37
Clients can access the branches using URLs with the ``bzr+ssh://`` prefix.  For
38
38
example, to get a local copy of the ProjectX trunk, a developer could do::
39
39
 
40
 
  $ bzr branch bzr+ssh://server.example.com/srv/bzr/projectx/trunk projectx
 
40
  $ brz branch bzr+ssh://server.example.com/srv/bzr/projectx/trunk projectx
41
41
 
42
42
If the developers have write access to the ``/srv/bzr/projectx`` directory, then
43
43
they can create new branches themselves using::
44
44
  
45
 
  $ bzr branch bzr+ssh://server.example.com/srv/bzr/projectx/trunk \
 
45
  $ brz branch bzr+ssh://server.example.com/srv/bzr/projectx/trunk \
46
46
  bzr+ssh://server.example.com/srv/bzr/projectx/feature-gui
47
47
 
48
48
Of course, if this isn't desired, then developers should not have write access
55
55
shared repository to hold all of the branches.  To set this up, do::
56
56
 
57
57
  $ cd /srv/bzr
58
 
  $ bzr init-repo --no-trees projectx
 
58
  $ brz init-repo --no-trees projectx
59
59
 
60
60
The ``--no-trees`` option saves space by not creating a copy of the working
61
61
files on the server's filesystem.  Then, any branch created under
69
69
``BZR_REMOTE_PATH`` environment variable.  For example, if the Bazaar executable
70
70
is installed in ``/usr/local/bzr-2.0/bin/bzr``, then a developer could use::
71
71
 
72
 
  $ BZR_REMOTE_PATH=/usr/local/bzr-2.0/bin/bzr bzr info \
 
72
  $ brz_REMOTE_PATH=/usr/local/bzr-2.0/bin/bzr bzr info \
73
73
  bzr+ssh://server.example.com/srv/bzr/proectx/trunk
74
74
 
75
75
to get information about the trunk branch.  The remote path can also be
81
81
refer to the home directory of user ``username``.  For example, if there are two
82
82
developers ``alice`` and ``bob``, then Bob could use::
83
83
 
84
 
  $ bzr log bzr+ssh://server.example.com/~/fix-1023
 
84
  $ brz log bzr+ssh://server.example.com/~/fix-1023
85
85
 
86
86
to refer to one of his bug fix branches and::
87
87
 
88
 
  $ bzr log bzr+ssh://server.example.com/~alice/fix-2047
 
88
  $ brz log bzr+ssh://server.example.com/~alice/fix-2047
89
89
  
90
90
to refer to one of Alice's branches. [#]_
91
91
 
133
133
 
134
134
If Alice logs in she uses the following command for her fix-1023 branch::
135
135
 
136
 
  $ bzr log bzr+ssh://bzruser@server.example.com/fix-1023
 
136
  $ brz log bzr+ssh://bzruser@server.example.com/fix-1023
137
137
 
138
138
If Repo Manager logs in he uses the following command to access Alice's
139
139
fix-1023::
140
140
 
141
 
  $ bzr log bzr+ssh://bzruser@server.example.com/alice/fix-1023
 
141
  $ brz log bzr+ssh://bzruser@server.example.com/alice/fix-1023
142
142