On Wed, Mar 13, 2013 at 4:56 PM, <[email protected]> wrote: > On 2013/03/13 15:44:20, janek wrote: >> Ok, now i see what you mean. >> I think my problem was that, because of "however", i had thought that >> in the description you contrast some new behaviour with some other >> behaviour that existed already. As in "this patch makes $xxx and #xxx >> do blah. However, \xxx won't do blah - it continues to do foo as it >> used to". > > Sigh. "However," and "In contrast," mean _exactly_ the same. > Besides, \xxx is indeed untouched in behavior and continues to do foo > as it used to. It is now special-cased (while it shared code and > behavior with $ previously) but indeed, the behavior for it is exactly > the same as before.
:/ I was afraid there was something i missed. I apologize for being so dimwitted. Nevertheless, i think that using imperative for commit messages is a good idea anyway. Janek _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
