70
70
The centralized model can have some drawbacks. A centralized RCS requires
71
71
that one is able to connect to the server whenever one wants to do version
72
control work. This can be a bit of a problem if your server on some other
73
machine on the internet and you are not. Or, worse yet, you ''are'' on the
72
control work. This can be a bit of a problem if your server is on some other
73
machine on the internet and you are not. Or, worse yet, you **are** on the
74
74
internet but the server is missing!
76
76
Decentralized Revision Control Systems (which I'll call DRCS after this
90
90
a **revision** of the directory tree whenever the user asks.
92
92
Revision control software such as Bazaar can do much more than just
93
storage and performing undo. For example, with Bazaar developer can
94
take the modifications in one branch of software and apply them to
95
another, related, branch -- even if those changes exist in a branch owned
96
by somebody else. This allows developers to cooperate without giving write
93
storage and performing undo. For example, with Bazaar a developer can
94
take the modifications in one branch of software and apply them to a
95
related branch -- even if those changes exist in a branch owned by
96
somebody else. This allows developers to cooperate without giving
97
write access to the repository.
99
99
Bazaar remembers the ''ancestry'' of a revision: the previous revisions
100
100
that it is based upon. A single revision may have more than one direct
107
107
==============================
109
109
Bazaar installs a single new command, **bzr**. Everything else is a
110
subcommand of this. You can get some help with `bzr help`. There will be
110
subcommand of this. You can get some help with ``bzr help``. Some arguments
111
are grouped in topics: ``bzr help topics`` to see which topics are available.
113
113
One function of a version control system is to keep track of who changed
114
114
what. In a decentralized system, that requires an identifier for each
115
115
author that is globally unique. Most people already have one of these: an
116
email address. Bzr is smart enough to automatically generate an email
116
email address. Bazaar is smart enough to automatically generate an email
117
117
address by looking up your username and hostname. If you don't like the
118
118
guess that Bazaar makes, then three options exist:
120
120
1. Set an email address via ``bzr whoami``. This is the simplest way.
121
To set a global identity, use::
123
% bzr whoami 'Your Name <email@example.com>'
125
If you'd like to use a different address for a specific branch, enter
126
the branch folder and use::
128
% bzr whoami --branch 'Your Name <email@example.com>'
130
1. Setting the email address in the
131
``~/.bazaar/bazaar.conf`` [1]_ by adding the following lines. Please note that
132
``[DEFAULT]`` is case sensitive::
135
email= Your Name <email@isp.com>
137
As above, you can override this settings on a branch by branch basis by
138
creating a branch section in ``~/.bazaar/locations.conf`` and adding the
141
[/the/directory/to/the/branch]
142
email=Your Name <email@isp.com>
144
1. Overriding the two previous options by setting the global environment
145
variable ``$BZREMAIL`` or ``$EMAIL`` (``$BZREMAIL`` will take precedence)
146
to your full email address.
122
To set a global identity, use::
124
% bzr whoami "Your Name <email@example.com>"
126
If you'd like to use a different address for a specific branch, enter
127
the branch folder and use::
129
% bzr whoami --branch "Your Name <email@example.com>"
131
#. Setting the email address in the ``~/.bazaar/bazaar.conf`` [1]_ by
132
adding the following lines. Please note that ``[DEFAULT]`` is case
136
email=Your Name <email@isp.com>
138
As above, you can override this settings on a branch by branch basis
139
by creating a branch section in ``~/.bazaar/locations.conf`` and
140
adding the following lines::
142
[/the/path/to/the/branch]
143
email=Your Name <email@isp.com>
146
#. Overriding the two previous options by setting the global environment
147
variable ``$BZR_EMAIL`` or ``$EMAIL`` (``$BZR_EMAIL`` will take
148
precedence) to your full email address.
148
150
.. [1] On Windows, the users configuration files can be found in the
149
151
application data directory. So instead of ``~/.bazaar/branch.conf``
155
157
Creating a branch
156
158
=================
158
History is by default stored in the .bzr directory of the branch. There
159
will be a facility to store it in a separate repository, which may be
160
remote. We create a new branch by running **bzr init** in an existing
160
History is by default stored in the .bzr directory of the branch. In a
161
future version of Bazaar, there will be a facility to store it in a
162
separate repository, which may be remote.
164
We create a new branch by running ``bzr init`` in an existing directory::
185
186
% bzr add hello.txt
190
If you add the wrong file, simply use **bzr remove** to make it
191
unversioned again. This does not delete the working copy.
193
If you add the wrong file, simply use ``bzr remove`` to make it
194
unversioned again. This does not delete the working copy in this case,
195
though it may in others [2]_.
197
.. [2] ``bzr remove`` will remove the working copy if it is currently
198
versioned, but has no changes from the last committed version. You
199
can force the file to always be kept with the ``--keep`` option to
200
``bzr remove``, or force it to always be deleted with ``--force``.
196
205
All history is stored in a branch, which is just an on-disk directory
197
206
containing control files. By default there is no separate repository or
198
207
database as used in svn or svk. You can choose to create a repository if
199
you want to (see the **bzr init-repo** command). You may wish to do this
200
if you have very large branches, or many branches of a moderate sized
208
you want to (see the ``bzr init-repo`` command). You may wish to do this
209
if you have very large branches, or many branches of a moderately sized
203
212
You'll usually refer to branches on your computer's filesystem just by
204
213
giving the name of the directory containing the branch. bzr also supports
205
accessing branches over http, for example::
214
accessing branches over http and sftp, for example::
207
216
% bzr log http://bazaar-vcs.org/bzr/bzr.dev/
209
By installing bzr plugins you can also access branches over the sftp or
217
% bzr log sftp://bazaar-vcs.org/bzr/bzr.dev/
219
By installing bzr plugins you can also access branches using the rsync
222
See the `Publishing your branch`_ section for more about how to put your
223
branch at a given location.
212
225
Reviewing changes
213
226
=================
245
258
''patch'', ''diffstat'', ''filterdiff'' and ''colordiff''::
248
*** added file 'hello.txt'
261
=== added file 'hello.txt'
262
--- hello.txt 1970-01-01 00:00:00 +0000
263
+++ hello.txt 2005-10-18 14:23:29 +0000
255
With the ''-r'' option, the tree is compared to an earlier revision, or
268
With the ``-r`` option, the tree is compared to an earlier revision, or
256
269
the differences between two versions are shown::
258
271
% bzr diff -r 1000.. # everything since r1000
259
272
% bzr diff -r 1000..1100 # changes from 1000 to 1100
261
The --diff-options option causes bzr to run the external diff program,
274
The ``--diff-options`` option causes bzr to run the external diff program,
262
275
passing options. For example::
264
277
% bzr diff --diff-options --side-by-side foo
266
Some projects prefer patches to show a prefix at the start of the path for
267
old and new files. The --prefix option can be used to provide such a prefix.
279
Some projects prefer patches to show a prefix at the start of the path
280
for old and new files. The ``--prefix`` option can be used to provide
268
282
As a shortcut, ``bzr diff -p1`` produces a form that works with the
269
283
command ``patch -p1``.
280
294
The **commit** command takes a message describing the changes in the
281
295
revision. It also records your userid, the current time and timezone, and
282
296
the inventory and contents of the tree. The commit message is specified
283
by the ''-m'' or ''--message'' option. You can enter a multi-line commit
297
by the ``-m`` or ``--message`` option. You can enter a multi-line commit
284
298
message; in most shells you can enter this just by leaving the quotes open
285
299
at the end of the line.
296
310
Message from an editor
297
311
======================
299
If you use neither the `-m` nor the `-F` option then bzr will open an
313
If you use neither the ``-m`` nor the ``-F`` option then bzr will open an
300
314
editor for you to enter a message. The editor to run is controlled by
301
your `$EDITOR` environment variable or
302
add `editor` to ~/.bazaar/bazaar.conf; `$BZR_EDITOR` will override
303
the above mentioned editor options. If you quit the editor without
304
making any changes, the commit will be cancelled.
315
your ``$VISUAL`` or ``$EDITOR`` environment variable, which can be overridden
316
by the ``editor`` setting in ``~/.bazaar/bazaar.conf``; ``$BZR_EDITOR`` will
317
override either of the above mentioned editor options. If you quit the
318
editor without making any changes, the commit will be cancelled.
320
The file that is opened in the editor contains a horizontal line. The part
321
of the file below this line is included for information only, and will not
322
form part of the commit message. Below the separator is shown the list of
323
files that are changed in the commit. You should write your message above
324
the line, and then save the file and exit.
326
If you would like to see the diff that will be committed as you edit the
327
message you can use the ``--show-diff`` option to ``commit``. This will include
328
the diff in the editor when it is opened, below the separator and the
329
information about the files that will be committed. This means that you can
330
read it as you write the message, but the diff itself wont be seen in the
331
commit message when you have finished. If you would like parts to be
332
included in the message you can copy and paste them above the separator.
323
351
If you've made some changes and don't want to keep them, use the
324
352
**revert** command to go back to the previous head version. It's a good
325
idea to use **bzr diff** first to see what will be removed. By default the
353
idea to use ``bzr diff`` first to see what will be removed. By default the
326
354
revert command reverts the whole tree; if file or directory names are
327
given then only those ones will be affected. **revert** also clears the
355
given then only those ones will be affected. ``bzr revert`` also clears the
328
356
list of pending merges revisions.
334
362
such as editor backups, object or bytecode files, and built programs. You
335
363
can simply not add them, but then they'll always crop up as unknown files.
336
364
You can also tell bzr to ignore these files by adding them to a file
337
called ''.bzrignore'' at the top of the tree.
365
called ``.bzrignore`` at the top of the tree.
339
367
This file contains a list of file wildcards (or "globs"), one per line.
340
368
Typical contents are like this::
347
375
If a glob contains a slash, it is matched against the whole path from the
348
376
top of the tree; otherwise it is matched against only the filename. So
349
377
the previous example ignores files with extension ``.o`` in all
350
subdirectories, but this example ignores only config.h at the top level
378
subdirectories, but this example ignores only ``config.h`` at the top level
351
379
and HTML files in ``doc/``::
356
384
To get a list of which files are ignored and what pattern they matched,
357
use ''bzr ignored''::
385
use ``bzr ignored``::
360
388
config.h ./config.h
391
The **bzr log** command shows a list of previous revisions. The **bzr log
392
--forward** command does the same in chronological order to get most
419
The ``bzr log`` command shows a list of previous revisions. The ``bzr log
420
--forward`` command does the same in chronological order to get most
393
421
recent revisions printed at last.
395
As with bzr diff, bzr log supports the -r argument::
423
As with ``bzr diff``, ``bzr log`` supports the ``-r`` argument::
397
425
% bzr log -r 1000.. # Revision 1000 and everything after it
398
426
% bzr log -r ..1000 # Everything up to and including r1000
430
458
You can delete files or directories by just deleting them from the working
431
459
directory. This is a bit different to CVS, which requires that you also
434
**bzr remove** makes the file un-versioned, but does not delete
435
the working copy. This is useful when you add the wrong file, or decide
436
that a file should actually not be versioned.
462
``bzr remove`` makes the file un-versioned, but may or may not delete
463
the working copy [2]_. This is useful when you add the wrong file,
464
or decide that a file should actually not be versioned.
458
486
Often rather than starting your own project, you will want to submit a
459
change to an existing project. You can get a copy of an existing branch
460
by copying its directory, expanding a tarball, or by a remote copy using
461
something like rsync. You can also use bzr to fetch a copy. Because this
462
new copy is potentially a new branch, the command is called *branch*::
487
change to an existing project. To do this, you'll need to get a copy of
488
the existing branch. Because this new copy is potentially a new branch,
489
the command is called **branch**::
464
491
% bzr branch http://bazaar-vcs.org/bzr/bzr.dev
468
495
operations on it locally: log, annotate, making and merging branches.
469
496
There will be an option to get only part of the history if you wish.
498
You can also get a copy of an existing branch by copying its directory,
499
expanding a tarball, or by a remote copy using something like rsync.
471
501
Following upstream changes
472
502
==========================
488
518
Merging from related branches
489
519
=============================
491
If two branches have diverged (both have unique changes) then **bzr
492
merge** is the appropriate command to use. Merge will automatically
521
If two branches have diverged (both have unique changes) then ``bzr
522
merge`` is the appropriate command to use. Merge will automatically
493
523
calculate the changes that exist in the branch you're merging from that
494
524
are not in your branch and attempt to apply them in your branch.
501
If there is a conflict during a merge, 3 files with the same basename are
502
created. The filename of the common base is appended with .BASE, the
503
filename of the file containing your changes is appended .THIS and the
504
filename with the changes from the other tree is appended .OTHER.
505
Using a program such as kdiff3, you can now comfortably merge them into
506
one file. To commit you have to rename it to the original basename and
507
delete the other two files. As long as there exist files with .BASE, .THIS
508
or .OTHER the commit command will complain.
531
If there is a conflict during a merge, 3 files with the same basename
532
are created. The filename of the common base is appended with ".BASE",
533
the filename of the file containing your changes is appended with
534
".THIS" and the filename with the changes from the other tree is
535
appended with ".OTHER". Using a program such as kdiff3, you can now
536
comfortably merge them into one file. In order to commit you have to
537
rename the merged file (".THIS") to the original file name. To
538
complete the conflict resolution you must use the resolve command,
539
which will remove the ".OTHER" and ".BASE" files. As long as there
540
exist files with .BASE, .THIS or .OTHER the commit command will
545
% kdiff3 file.BASE file.OTHER file.THIS
510
549
[**TODO**: explain conflict markers within files]
518
557
directory. One can push a branch (or the changes for a branch) by one of
519
558
the following three methods:
521
* Rsync: rsync -avrz LOCALBRANCH servername.com/this/directory/here
523
(or any other tool for publishing a directory to a web site.)
525
* bzr push sftp://servername.com/this/directory/here
527
(The directory that must already exist)
529
* The rspush plugin that comes with BzrTools
560
* The best method is to use bzr itself to do it.
564
% bzr push sftp://servername.com/path/to/directory
566
(The destination directory must already exist unless the
567
``--create-prefix`` option is used.)
569
* Another option is the ``rspush`` plugin that comes with BzrTools, which
570
uses rsync to push the changes to the revision history and the working
573
You can also use copy the files around manually, by sending a tarball, or
574
using rsync, or other related file transfer methods. This is usually
575
less safe than using ``push``, but may be faster or easier in some
532
578
Moving changes between trees
533
579
============================
547
593
This will apply all of the uncommitted changes you made in OLDDIR to NEWDIR.
548
594
It will not apply committed changes, even if they could be applied to NEWDIR
549
with a regular merge. The changes will remain in OLDDIR, but you can use **bzr
550
revert OLDDIR** to remove them, once you're satisfied with NEWDIR.
595
with a regular merge. The changes will remain in OLDDIR, but you can use ``bzr
596
revert OLDDIR`` to remove them, once you're satisfied with NEWDIR.
552
598
NEWDIR does not have to be a copy of OLDDIR, but they should be related.
553
599
The more different they are, the greater the chance of conflicts.
added
removed
doc/en/tutorials/tutorial.txt
