On Mon, Apr 2, 2012 at 11:11 AM, Phil Holmes wrote:
> - Original Message - From: "Julien Rioux"
> To: ; ;
> ; ; ;
>
>
>> > A snippet with a deprecated option, triggering compatibility mode:
>> >
>> > -\lilypond[11pt,fragment]{c' e' g'}
>> > +\lilypond[staffsize=11,fragment]{c' e' g'}
>>
- Original Message -
From: "Julien Rioux"
To: ; ;
; ; ;
> A snippet with a deprecated option, triggering compatibility mode:
>
> -\lilypond[11pt,fragment]{c' e' g'}
> +\lilypond[staffsize=11,fragment]{c' e' g'}
>
> \end{document}
This change to tex-compatibility-mode.tex makes no sen
On Sun, Apr 1, 2012 at 2:32 PM, wrote:
> Reviewers: Julien Rioux, Graham Percival, dak,
>
> Message:
> Please review
>
> Description:
> These files used what appears to be a deprecated syntax to invoke
> lilypond-book, resulting in these warnings:
>
> lilypond-book.py: warning: deprecated ly-opti
On Sun, Apr 01, 2012 at 03:16:52PM +0100, Phil Holmes wrote:
> It looked fine on Rietveld when I looked, and I couldn't find the
> exceptions bit in the CG, so it's pushed to staging as is.
Oops, we were smarter than I thought -- the exceptions are built
into git-cl precisely to avoid problems of
- Original Message -
From:
To: ; ;
Cc: ;
Sent: Sunday, April 01, 2012 2:23 PM
Subject: Re: Changes .tex files to get rid of warning (issue 5976055)
The .latex file just says "upload in progress". Could you add it to the
exceptions (like .scm and .ps) as discussed somewh
The .latex file just says "upload in progress". Could you add it to the
exceptions (like .scm and .ps) as discussed somewhere in the CG?
Assuming that the change to the .latex file is just like the .lytex
ones, please push the whole thing directly to staging.
(I'd still like the .latex extension
Reviewers: Julien Rioux, Graham Percival, dak,
Message:
Please review
Description:
These files used what appears to be a deprecated syntax to invoke
lilypond-book, resulting in these warnings:
lilypond-book.py: warning: deprecated ly-option used: 11pt=None
lilypond-book.py: warning: compatibili
