Lines Matching refs:change

100 Even trivial patches must have a change log entry in the usual format (see
101 ChangeLog). Refer to bug numbers in the change log if relevant.
141 If you make a change visible to the user in some way, you should check the
149 Your cvs commit message only needs to briefly describe what your change
150 does - the change log should have the detailed description. Any
151 non-trivial change needs approval from either John, Phil or Maynard,
155 not need a change log, and neither does changes to TODO. If you make a
156 change that affects the user (feature improvement, new feature, bug fix,
157 UI change), see the next section.
166 the CVS code. This means that if you make a user-visible change as described
172 Any user-visible change should have a short description in the file