36
36
pqm@pqm.ubuntu.com-20071129184101-u9506rihe4zbzyyz
38
While these identifiers are necessary for internal use and external tool
39
integration, branch-specific *revision numbers* are the preferred
40
interface for humans. Typical revision numbers are 1, 42 and 2977.1.59.
38
Revision-ids are generated at commit time or, for imports from other
39
systems, at the time of import. While revision-ids are necessary
40
for internal use and external tool integration, branch-specific
41
*revision numbers* are the preferred interface for humans.
43
Revision numbers are dotted decimal identifiers like 1, 42 and 2977.1.59
44
that trace a path through the revision number graph for a branch.
45
Revision numbers are generally shorter than revision-ids and,
46
within a single branch, can be compared with each other to get a sense
47
of their relationship. For example, revision 10 is the mainline (see below)
48
revision immediately after revision 9. Revision numbers
49
are generated on the fly when commands are executing, because they
50
depend on which revision is the tip (i.e. most recent revision)
41
53
See `Specifying revisions`_ in the appendices for a closer look at
42
54
the numerous ways that revisions and ranges of revisions can be specified
43
55
in Bazaar, and `Understanding Revision Numbers`_ for a more detailed
62
74
In the simplest case, a branch is an *ordered series of revisions*.
63
The last revision is known as the *head*.
75
The last revision is known as the *tip*.
65
77
Branches may split apart and be *merged* back together, forming a
66
78
*graph* of revisions. Technically, the graph shows directed relationships
added
removed
doc/en/user-guide/core_concepts.txt
