Hi,
It looks like the RELEASE_NOTES is fixed, but the manual additions I made were
lost during the fix. Namely,
revision 2.318
date: 2008-07-21 16:03:41 +0300; author: sayar; state: Exp; lines: +3 -0;
commitid: coI8nVhRm
7TKIFbt;
Added a check to rattle.h to make sure that time_step is defined before
defining a rigid_bond.
----------------------------
revision 2.317
date: 2008-07-21 15:56:56 +0300; author: sayar; state: Exp; lines: +3 -0;
commitid: kGL1NSF1H
K2oGFbt;
Added a check to angle.h for dot product exceeding 1.0 due to floating
point arithmetic.
These should be added to the RELEASE_NOTES manual once again. The relevant
changes to the c code are already committed to the CVS.
Could the maintainers of the cronjob code some how fix this, or tell me how to
fix it?
Greetings from Istanbul,
Mehmet
Axel Arnold wrote:
Am Dienstag 22 Juli 2008 10:15 schrieb Mehmet Sayar:
Hi All,
The release notes seem to be chopped up by a cronjob.
After I committed two changes to cvs yesterday, I updated my Espresso this
morning. The only change was done by a cronjob which cut 75 lines.
Could someone explain what is going on? What does this cronjob do?
Hi all,
since quite some time, RELEASE_NOTES entries are generated by a cronjob from
the CVS logs. This works as follows:
- a line in the log starting with [NEW] describes a new feature
- a line starting with [BUGFIX] or [FIX] marks a bugfix
- a line starting with [CHANGE] markes a change to an existing feature
- if you need several lines to describe a change, you can tag blocks. All
lines starting with [NEW0] will describe one new feature, all lines with
[NEW1] another feature, and so on.
However, it seems as if the cronjob deletes manually entered entries. The
maintainers of the script should look into that.
Many regards,
Axel