- Original Message -
From: "Thomas Morley"
To: "lilypond-devel"
Sent: Friday, December 28, 2018 12:13 PM
Subject: makelsr
Hi all,
I think we need some guidelines in the case a new lsr-snippet is used
for the docs.
See https://sourceforge.net/p/testlilyissues/issues/5251/
James aske
James Lowe writes:
> David,
>
> On 28/12/2018 14:13, David Kastrup wrote:
>> Thomas Morley writes:
>>
>>> Hi all,
>>>
>>> I think we need some guidelines in the case a new lsr-snippet is used
>>> for the docs.
>>> See https://sourceforge.net/p/testlilyissues/issues/5251/
>>>
>>> James askes not
Thomas et al.
On 28/12/2018 14:13, David Kastrup wrote:
Thomas Morley writes:
Hi all,
I think we need some guidelines in the case a new lsr-snippet is used
for the docs.
See https://sourceforge.net/p/testlilyissues/issues/5251/
James askes not to run makelsr, because a plethora of changes w
David,
On 28/12/2018 14:13, David Kastrup wrote:
Thomas Morley writes:
Hi all,
I think we need some guidelines in the case a new lsr-snippet is used
for the docs.
See https://sourceforge.net/p/testlilyissues/issues/5251/
James askes not to run makelsr, because a plethora of changes will
clu
Thomas Morley writes:
> Hi all,
>
> I think we need some guidelines in the case a new lsr-snippet is used
> for the docs.
> See https://sourceforge.net/p/testlilyissues/issues/5251/
>
> James askes not to run makelsr, because a plethora of changes will
> clutter the patch-set.
> OTOH, a patch can
Am 28.12.18 um 13:13 schrieb Thomas Morley:
James askes not to run makelsr, because a plethora of changes will
clutter the patch-set.
OTOH, a patch can't stand alone and can't be applied for testings by
reviewers without makelsr. So I voted for doing makelsr.
The CG is not clear in this regard
Hi all,
I think we need some guidelines in the case a new lsr-snippet is used
for the docs.
See https://sourceforge.net/p/testlilyissues/issues/5251/
James askes not to run makelsr, because a plethora of changes will
clutter the patch-set.
OTOH, a patch can't stand alone and can't be applied for
On 2018/12/28 09:43:58, Valentin Villenave wrote:
On 2018/12/21 17:50:33, Valentin Villenave wrote:
> Correct convert rules.
OK, pushed onto staging as 72067b395d947f1349ab8010f0592d45e52b8141.
I think you should change the sourceforge issue
(https://sourceforge.net/p/testlilyissues/issues/4
On 2018/12/21 17:50:33, Valentin Villenave wrote:
Correct convert rules.
OK, pushed onto staging as 72067b395d947f1349ab8010f0592d45e52b8141.
https://codereview.appspot.com/369930043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://li
