Hi!
I like the new changelog. I just wanted to comment on that given
current practices I see.
W liście z sob, 10-01-2004, godz. 05:41, Arnaud Vandyck pisze:
> kaffe (1:1.1.3-0.1) unstable; urgency=low
>
> * Non Maintainer Upload.
> * New upstream release (Closes: #215095).
exactly: information what happened goes first, then no. of bugreport.
> - Closes: #225702
> kaffe FTBFS on m68k
> Already explained in the bug report, also, see kaffe changelog:
> 2003-08-28 Guilhem Lavaux <[EMAIL PROTECTED]>
> - Closes: #225691
> kaffe FTBFS on alpha
> Already explained in the bug report, also, see kaffe changelog:
> 2003-09-01 Jim Pick <[EMAIL PROTECTED]>
Some would write:
- Fixed FTBFS om m68k and alpha. Closes #225702, #225691. See BTS
or kaffe changelog (2003-08-28 and 2003-09-01) for details.
> - Closes: #207998
> Passing extra JNI directories breaks bootstrap classes
> Already explained in the bug report, also, see kaffe changelog:
> 2003-10-06 Dalibor Topic <[EMAIL PROTECTED]>
- Passing extra JNI directories doesn't break bootstrap classes
anymore. Closes: #207998) See bugreport of kaffe changelog
(2003-10-06)
Again - what changed (got fixed), then the no of bug and further info.
> * debian/control (Provides): java-compiler (Closes: #225262).
what about:
* debian/control: added Provides: java-compiler (Closes: #225262).
> * debian/postinst, debian/prerm: added javac as an alternative
> (Closes: #206644).
The general practise I see is to include the information what actually
got changed - first. Because bug no. is non-informative, while this
gives good overview of the changes from the first sight.
Great work, Arnaud!
Grzegorz B. Prokopski
--
Grzegorz B. Prokopski <[EMAIL PROTECTED]>
Debian GNU/Linux http://www.debian.org
SableVM - LGPLed JVM http://www.sablevm.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
