/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/en/developer-guide/HACKING.txt

  • Committer: Andrew Bennetts
  • Date: 2009-06-15 06:47:14 UTC
  • mfrom: (4438 +trunk)
  • mto: This revision was merged to the branch mainline in revision 4446.
  • Revision ID: andrew.bennetts@canonical.com-20090615064714-j04tkbgfz6bis3la
Merge bzr.dev.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/developer-guide/HACKING.txt
46
46
If nothing else, perhaps you'll find inspiration in how other developers
47
47
have solved their challenges.
48
48
 
 
49
Finding Something To Do
 
50
=======================
 
51
 
 
52
Ad-hoc performance work can also be done. One useful tool is the 'evil' debug
 
53
flag. For instance running ``bzr -Devil commit -m "test"`` will log a backtrace
 
54
to the bzr log file for every method call which triggers a slow or non-scalable
 
55
part of the bzr library. So checking that a given command with ``-Devil`` has
 
56
no backtraces logged to the log file is a good way to find problem function
 
57
calls that might be nested deep in the code base.
49
58
 
50
59
Planning and Discussing Changes
51
60
===============================