Lines Matching refs:change
27 - a short description of each functional change,
28 - a short description of each technical change impacting the users.
31 code change (or as part of the last committed change) that fixes the
32 bug or implements the new feature/technical change.
34 the code change.
41 Once you have commit the change, update the bug status in bugzilla,
51 Implementing a change
53 When implementing a functional or 'user impacting' technical change,
54 add a short description of the change in the relevant sub-section
61 possible to commit the NEWS change together with the code changes.
62 In such a case, first commit the VEX change. Then just after, commit
63 the NEWS change. In the bugzilla status, reference (at least) the Valgrind
70 earlier commits, using the word 'PARTIAL' to indicate that the change or