← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/en/user-guide/bug_trackers.txt

  • Committer: Alexander Belchenko
  • Date: 2007-12-05 20:12:27 UTC
  • mfrom: (3079 +trunk)
  • mto: This revision was merged to the branch mainline in revision 3083.
  • Revision ID: bialix@ukr.net-20071205201227-9uiwuzrgzge15e5e
merge bzr.dev

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/user-guide/bug_trackers.txt
12
12
When you make a commit you can assiociate it with a bug by using the
13
13
``--fixes`` option of ``commit``. For example::
14
14
 
15
 
    $ bzr commit --fixes 12345 -m "Properly close the connection on errors"
 
15
    $ bzr commit --fixes project:12345 -m "Properly close the connection"
16
16
 
17
17
This will set a revision property on the revision that is committed
18
18
which contains the URI at which more information on the bug can be found.
65
65
would allow ``bzr commit --fixes twisted:1234`` to mark Twisted's bug 1234 as
66
66
fixed.
67
67
 
 
68
bugtracker_<tracker_abbrevation>_url
 
69
------------------------------------
 
70
If present, the location of a generic bug tracker instance referred to by
 
71
<tracker_abbreviation>. The location must contain an ``{id}`` placeholder,
 
72
which will be replaced by a specific bug ID. This option can then be used
 
73
together with ``bzr commit --fixes`` to mark bugs in that tracker as being
 
74
fixed by that commit. For example::
 
75
 
 
76
    bugtracker_python_url = http://bugs.python.org/issue{id}
 
77
 
 
78
would allow ``bzr commit --fixes python:1234`` to mark bug 1234 in Python's
 
79
Roundup bug tracker as fixed, or::
 
80
 
 
81
    bugtracker_cpan_url = http://rt.cpan.org/Public/Bug/Display.html?id={id}
 
82
 
 
83
for CPAN's RT bug tracker.
 
84
 
68
85
Limitations of the system
69
86
-------------------------
70
87