4
Bazaar repositories support setting of a key/value pairs for each revision.
5
Applications can use these properties to store additional information
11
In general, revision properties are set by passing keyword argument
12
``revprops`` to method ``MutableTree.commit``. For example::
15
properties['my-property'] = 'test'
16
tree.commit(message, revprops=properties)
18
Properties can be retrieved via the attribute ``properties`` of
19
instances of the class ``Revision``::
21
if 'my-property' in revision.properties:
22
my_property = revision.properties['my-property']
28
At the moment, three standardized revision properties are recognized and used
31
* ``authors`` - Authors of the change. This value is a "\\n" separated set
32
of values in the same format as the committer-id. This property can be
33
set by passing a list to the keyword argument ``authors`` of the function
34
``MutableTree.commit``.
35
* ``author`` - Single author of the change. This property is deprecated in
36
favour of ``authors``. It should no longer be set by any code, but will
37
still be read. It is ignored if ``authors`` is set in the same revision.
38
* ``branch-nick`` - Nickname of the branch. This can be specified by the user,
39
but it defaults to the colocated branch name or the branch's directory name.
40
The value is set automatically in ``MutableTree.commit``.
41
* ``bugs`` - A list of bug URLs and their statuses. The list is separated
42
by the new-line character (\\n) and each entry is in format
43
'<URL> <status>'. Currently, bzrlib uses only status 'fixed'. See
44
`Bug Trackers`_ for more details about using this feature.
46
.. _Bug Trackers: ../en/user-guide/index.html#bug-trackers