"Phil Holmes" writes:
> From: "David Kastrup"
>>
>> Let's cut this short. Test this patch first. If it fixes the problem,
>> the bisection is pointless.
>
>
> That fixes it. Can you push the patch to staging?
I pushed a variant of it to staging (one without the change in
version/timestamp th
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc: "James Lowe" ;
Sent: Tuesday, May 26, 2015 12:43 PM
Subject: Re: PDF is broken for @notation{} encoding
"Phil Holmes" writes:
- Original Message -
From: "David
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To: "Phil Holmes"
> Cc: "James Lowe" ;
> Sent: Tuesday, May 26, 2015 11:57 AM
> Subject: Re: PDF is broken for @notation{} encoding
>> Huh. Git bi
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc: "James Lowe" ;
Sent: Tuesday, May 26, 2015 11:57 AM
Subject: Re: PDF is broken for @notation{} encoding
Huh. Git bisect would have heeded the _topological_ order and would
have made it mo
"Phil Holmes" writes:
> From: "David Kastrup"
>
>> I'm still flabbergasted at the supposed faulty commit. Here is one
>> theory I'd consider more plausible:
>>
>> commit 5eca56fae0faa2db9cf7f12903e1a06c42b2af0d
>> Author: Walter Garcia-Fontes
>> Date: Sat Feb 7 20:00:15 2015 +0100
>>
>>D
- Original Message -
From: "David Kastrup"
To: "James Lowe"
Cc:
Sent: Tuesday, May 26, 2015 10:07 AM
Subject: Re: PDF is broken for @notation{} encoding
James Lowe writes:
On 26/05/15 08:35, David Kastrup wrote:
James Lowe writes:
On 25/05/15 16:08, Phil
James Lowe writes:
> On 26/05/15 08:35, David Kastrup wrote:
>> James Lowe writes:
>>
>>> On 25/05/15 16:08, Phil Holmes wrote:
I can try again, but it was consistent. James might want to try?
>>>
>>> If it helps.
>>>
>>> I get the same thing too.
>>
>> How much effort is it to do one it
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To: "James Lowe"
> Cc: "Phil Holmes" ;
> Sent: Tuesday, May 26, 2015 9:02 AM
> Subject: Re: PDF is broken for @notation{} encoding
>
>
>
- Original Message -
From: "David Kastrup"
To: "James Lowe"
Cc: "Phil Holmes" ;
Sent: Tuesday, May 26, 2015 9:02 AM
Subject: Re: PDF is broken for @notation{} encoding
James Lowe writes:
On 26/05/15 08:35, David Kastrup wrote:
James Lowe wri
James Lowe writes:
> On 26/05/15 08:35, David Kastrup wrote:
>> James Lowe writes:
>>
>>> On 25/05/15 16:08, Phil Holmes wrote:
I can try again, but it was consistent. James might want to try?
>>>
>>> If it helps.
>>>
>>> I get the same thing too.
>>
>> How much effort is it to do one it
On 26/05/15 08:35, David Kastrup wrote:
> James Lowe writes:
>
>> On 25/05/15 16:08, Phil Holmes wrote:
>>> I can try again, but it was consistent. James might want to try?
>>
>> If it helps.
>>
>> I get the same thing too.
>
> How much effort is it to do one iteration on one affected file? I
James Lowe writes:
> On 25/05/15 16:08, Phil Holmes wrote:
>> I can try again, but it was consistent. James might want to try?
>
> If it helps.
>
> I get the same thing too.
How much effort is it to do one iteration on one affected file? I have
absolutely no clue how this may come about so if
On 25/05/15 16:08, Phil Holmes wrote:
> I can try again, but it was consistent. James might want to try?
If it helps.
I get the same thing too.
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypo
Keith OHara writes:
> Phil Holmes philholmes.net> writes:
>
>> >> > whenever we use notation{text}, then there is a paragraph break
> before
>> >> > the "text". It took a while to figure out the guilty commit, but it is
>> >> > 9f3c7711bb73baf3aea8502227fb5fd2d2851753: "update texinfo.tex fr
Phil Holmes philholmes.net> writes:
> >> > whenever we use notation{text}, then there is a paragraph break
before
> >> > the "text". It took a while to figure out the guilty commit, but it is
> >> > 9f3c7711bb73baf3aea8502227fb5fd2d2851753: "update texinfo.tex from
> >> > upstream".
> >> >
I
- Original Message -
From: "Phil Holmes"
To: "David Kastrup"
Cc:
Sent: Monday, May 25, 2015 4:08 PM
Subject: Re: PDF is broken for @notation{} encoding
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Monda
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Monday, May 25, 2015 4:00 PM
Subject: Re: PDF is broken for @notation{} encoding
Phil Holmes writes:
> Look at page 22 of the most recent PDF of Learning, and you'll see that
>
Phil Holmes writes:
> Look at page 22 of the most recent PDF of Learning, and you'll see that
> whenever we use @notation{text}, then there is a paragraph break before
> the "text". It took a while to figure out the guilty commit, but it is
> 9f3c7711bb73baf3aea8502227fb5fd2d2851753: "update t
Look at page 22 of the most recent PDF of Learning, and you'll see that
whenever we use @notation{text}, then there is a paragraph break before
the "text". It took a while to figure out the guilty commit, but it is
9f3c7711bb73baf3aea8502227fb5fd2d2851753: "update texinfo.tex from
upstream".
A
19 matches
Mail list logo
