| 1 | ␉This file is no longer used. Monotone developers' convention is␊ |
| 2 | ␉now to write ChangeLog-format log messages in the commit logs␊ |
| 3 | ␉only.␊ |
| 4 | ␊ |
| 5 | ␉Many people were duplicating the same text in both places, and␊ |
| 6 | ␉this caused unnecessary merge conflicts for ordering of the␊ |
| 7 | ␉serialised ChangeLog file for the non-serialised ancestry graph.␊ |
| 8 | ␊ |
| 9 | ␉"mtn log" will produce the same information, sorted in proper␊ |
| 10 | ␉ancestry order, even with the presence of propagates and putbacks␊ |
| 11 | ␉of long-running development branches. A copy of this output will␊ |
| 12 | ␉overwrite this file for release tarballs.␊ |
| 13 | ␊ |
| 14 | ␉When writing commit log messages in ChangeLog format, you can omit␊ |
| 15 | ␉the date and name header, because these will be carried in the␊ |
| 16 | ␉author and date certs. Just use the body part, like so:␊ |
| 17 | ␊ |
| 18 | ␊ |
| 19 | ␉* foo.cc (function): change this to foo more efficiently␊ |
| 20 | ␉* cmd_bar.cc: use the more efficient foo␊ |
| 21 | ␉* NEWS: tell the users that the bar command is now so much faster.␊ |
| 22 | ␉ |
