| 1 |
Epiphany doesn't use ChangeLog anymore. Instead, we use Git checkin comments |
| 2 |
to autogenerate a ChangeLog file at "make dist" time. |
| 3 |
|
| 4 |
When committing a patch to git, you must use a checkin comment that fully |
| 5 |
describes the changes made. If the checkin is related to a bug, reference |
| 6 |
the bug number. Example: |
| 7 |
|
| 8 |
When removing a toolbar, make its items available again in the toolbar |
| 9 |
editor. (Bug #131182) |
| 10 |
|
| 11 |
If there is no bug report that records who approved the patch for commit, |
| 12 |
you must add that information to the checkin comment, e.g. "approved by chpe |
| 13 |
on IRC" (unless you're a core contributors and thus can self-approve your |
| 14 |
commits). |
| 15 |
|
| 16 |
Checkin comments MUST use the UTF-8 encoding. |
| 17 |
|
| 18 |
If you forget to check in some changes that belonged in the same commit (e.g. |
| 19 |
you accidentally omitted a file), you must copy the checkin comment from the |
| 20 |
previous, incomplete checkin, and additionally reference that commit's svn |
| 21 |
revision number. |
| 22 |
|
| 23 |
DO NOT use meaningless checkin comments such as "forgotten file" ! |
| 24 |
|
| 25 |
If you make a major mistake in the checkin comment (e.g it is empty, or |
| 26 |
you've forgotten to cite the bug numbers), you must create a new checkin |
| 27 |
that touches all files the original checkin changed (just using whitespace |
| 28 |
changes preferably, or fix a random typo), and in the new checkin comment |
| 29 |
you must note that this new checkin fixes the original checkin, referencing |
| 30 |
it by its SVN revision number. |
| 31 |
|
| 32 |
Do NOT commit to this module without permission from a maintainer. |
| 33 |
See the MAINTAINERS file for who they are. |