4 LilyPond development moves quickly, so if you have a problem, it is
5 wise to check if it has been fixed in a newer release. If you think
6 you found a bug, please send in a bugreport including the following
11 @item @strong{important:} a sample input which causes the error.
13 (and you will do us a favor if send a @strong{small} sample file)
15 @item @strong{important:} which LilyPond version you use.
17 This information tells us if you've found a new bug, or an old one.
19 @item A description of the platform you use (i.e., operating system,
20 system libraries, whether you downloaded a binary release)
22 @item If necessary, send a description of the bug itself.
27 You can send the report to @email{bug-gnu-music@@gnu.org}---You don't
28 have to be subscribed to this mailinglist, or you can enter the bug in
30 @uref{http://appel.lilypond.org/wiki?LilyPondBugs}.