/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/developers/development-repo.txt

  • Committer: Jelmer Vernooij
  • Date: 2018-06-14 17:59:16 UTC
  • mto: This revision was merged to the branch mainline in revision 7065.
  • Revision ID: jelmer@jelmer.uk-20180614175916-a2e2xh5k533guq1x
Move breezy.plugins.git to breezy.git.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/development-repo.txt
44
44
   development version available before pulling in bzr.dev changes
45
45
   around release time, as that is when old format cleanups will occur.
46
46
 
47
 
We cannot guarantee backwards compatibility though, because some of the
 
47
We cannot guarantee backwards compatability though, because some of the
48
48
planned work may be 'upgrade only'. Please see ``bzr help formats`` for
49
49
the text of the 'development' format which will indicate its
50
 
compatibility with other formats if you need to interoperate with
 
50
compatability with other formats if you need to interoperate with
51
51
users or services that do not have bzr.dev.
52
52
 
53
53
Before converting to a development format
89
89
for branches, you can make it a ``development`` repository like this::
90
90
 
91
91
  cd my-repo
92
 
  bzr init-shared-repo --development .
 
92
  bzr init-repo --development .
93
93
  cd my-stuff
94
94
  bzr init
95
95
  bzr add
96
96
  bzr commit -m "initial import"
97
97
 
98
98
In other words, use the normal sequence of commands but add the
99
 
``--development`` option to the ``init-shared-repo`` command.
 
99
``--development`` option to the ``init-repo`` command.
100
100
 
101
101
Upgrading an existing branch or repository to development
102
102
---------------------------------------------------------
141
141
Here are the commands for the shared repository approach::
142
142
 
143
143
  cd my-repo
144
 
  bzr init-shared-repo --development .
 
144
  bzr init-repo --development .
145
145
  bzr branch my-source-branch my-new-branch
146
146
  cd my-new-branch
147
147
 
171
171
 
172
172
If you need any help or encounter any problems, please contact the developers
173
173
via the usual ways, i.e. chat to us on IRC or send a message to our mailing
174
 
list. See https://www.breezy-vcs.org/pages/support.html for contact details.
 
174
list. See http://wiki.bazaar.canonical.com/BzrSupport for contact details.
175
175
 
176
176
 
177
177
Technical notes