lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond ./ChangeLog Documentation/user/instrum...


From: Han-Wen Nienhuys
Subject: Re: lilypond ./ChangeLog Documentation/user/instrum...
Date: Thu, 28 Apr 2005 10:02:58 +0200

Op wo, 27-04-2005 te 19:45 -0400, schreef Jürgen Reuter:
> CVSROOT:      /cvsroot/lilypond
> Module name:  lilypond
> Branch:       
> Changes by:   Jrgen Reuter <address@hidden>   05/04/27 23:45:43
> 
> Modified files:
>       .              : ChangeLog 
>       Documentation/user: instrument-notation.itely 
>       lily           : mensural-ligature.cc 
>                        vaticana-ligature-engraver.cc 
>       lily/include   : mensural-ligature.hh 
>       mf             : parmesan-heads.mf 
> 
> Log message:
>       * lily/vaticana-ligature-engraver.cc (need_extra_space): renamed
>       to need_extra_horizontal_space; bugfix: use class scope to avoid
>       global namespace pollution
>       
>       * Documentation/user/instrument-notation.itely (ligatures): added
>       comment on possible future syntax change and how to work around
>       
>       * lily/vaticana-ligature-engraver.cc, mf/parmesan-heads.mf
>       (epiphonus, cephalicus): fine-tune shape of plica head for narrow
>       intervals (fixes agnus dei example)
>       
>       * lily/include/mensural-ligature.hh: make comments clearer
>       
>       * lily/mensural-ligature.cc: line thickness of flexa shape
>       (originally by Pal Benko; slightly modified)
>       
>       * Documentation/user/instrument-notation.itely (white mensural
>       ligatures): selected a more illustrative example

Am I correct that this is actually Pal Benko's patch? If yes, can you
clearly mark that as such in the ChangeLog? We want to be able to track
backwards the copyright status of each file.

thanks,

-- 
Han-Wen Nienhuys - address@hidden
LilyPond Software Design - http://www.lilypond-design.com





reply via email to

[Prev in Thread] Current Thread [Next in Thread]