Lines Matching refs:should

13 the code should explain the code's present state, but ChangeLog
14 entries should explain how and when it got that way.  The ChangeLog
28 Every change to the sources should have a ChangeLog entry.  The value
35 each year, the ChangeLog should be renamed to "ChangeLog-YYYY", and a
42 ChangeLog entries should be full sentences, not sentence fragments.
46 further details should appear in the source code.
48 The log entry should mention every file changed.  It should also
67 Each paragraph should be a set of changes that accomplish a single
68 goal.  Independent changes should be in separate paragraphs.  For
91 The header line for the ChangeLog entry should have the format shown
98 One should never need the ChangeLog to understand the current code.
100 ChangeLog, you should consider carefully whether your text doesn't
126 "New Function" --- all the details should be in the source.
165 ChangeLog, so we maintain both.  When you commit a change, you should
178 case, what position and date should the developer use for the
186   ChangeLog entry should be written as normal, inserted at the top of
191   the ChangeLog entry should have the following form:
204   As shown here, the entry for the merge should be like any other
206   the date the merge was committed.  It should indicate the origin of