James Lowe writes:
> Hello,
>
> On 03/02/16 19:26, David Kastrup wrote:
>> Paul Morris writes:
>>
On Feb 3, 2016, at 1:38 PM, David Kastrup wrote:
> Can someone help? Or perhaps remove these entries from staging for the
> time being?
I'll back out issue 4752 and let you c
Am 03.02.2016 um 12:14 schrieb Federico Bruni:
> Hi Urs
>
> I jump in late to ask if the transition to texi2any might be added to
> the list.
> It might not be a sexy project but it's very needed and we all know
> how much the documentation is important for LilyPond.
>
> If Graham confirms his av
Hi Paul,
Am 27.01.2016 um 02:37 schrieb Paul Morris:
> While we’re at it, one thing I’ve thought about is simplifying vertical
> spacing changes. Basically something like this[1] but possibly integrated
> into LilyPond. One idea is that alongside padding, minimum-distance, and
> basic-distanc
Section 2.5 of the Mentoring Organization agreement specifies that projects
cannot be documentation.
http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/org_admin_agreement
So it seems to me that unless we turn this project into a texi2html-to-texi2any
translator, it
Hi Urs,
> On Feb 4, 2016, at 4:20 AM, Urs Liska wrote:
>
> Hi Paul,
>
> Am 27.01.2016 um 02:37 schrieb Paul Morris:
>> While we’re at it, one thing I’ve thought about is simplifying vertical
>> spacing changes. Basically something like this[1] but possibly integrated
>> into LilyPond. One i
> On Feb 4, 2016, at 5:20 AM, Carl Sorensen wrote:
>
> Section 2.5 of the Mentoring Organization agreement specifies that projects
> cannot be documentation.
>
> http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/org_admin_agreement
>
> So it seems to me that unless
> On Feb 3, 2016, at 2:26 PM, David Kastrup wrote:
>
> Different GCC versions are a typical cause. Not using
> --disable-optimising (alternatively --enable-checking) when testing is
> another. Having forgotten to check in some new file also happens
> regularly.
Thanks, I tried --disable-optimi
