Fails make.
https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/common-notation.itely
File Documentation/learning/common-notation.itely (right):
https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/common-notation.itely#newcode119
Documentation/learn
> It depends on which part of LilyPond you want to help with as to the
> availability of people to help you. Is there a particular skill-set, set
> of issues or area of LilyPond you are particularly interested in?
Thank you for responding. I would like to be able to contribute code to the
project
On 08/12/14 20:37, Urs Liska wrote:
>
> Am 08.12.2014 21:24, schrieb paulwmor...@gmail.com:
>> One more thing.
>>
>>
>> https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi
>>
>> File Documentation/web/community.itexi (right):
>>
>> https://codereview.appspot.com/1
Hello Kevin,
On 08/12/14 20:08, Kevin Barry wrote:
> Dear Lilypond developers,
>
> I read in the contributor's guide that there is a system of mentorship for
> people who would like to help the project. Is that still the case? And if
> so how do I get involved in it.
>
> Kevin
Thank you for tak
> On Dec 8, 2014, at 08:21 , David Kastrup wrote:
>
> Masamichi HOSODA writes:
>
>>> I agree that changing the algorithms is preferred; I didn’t mean to
>> suggest otherwise. But if that’s not going to happen overnight, and
>> there is a way to mitigate the problem in the meantime without
>>
LGTM, just caught a few minor things. -Paul
https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):
https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#newcode897
Documentation/web/c
Am 08.12.2014 21:24, schrieb paulwmor...@gmail.com:
One more thing.
https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):
https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#ne
One more thing.
https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):
https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#newcode965
Documentation/web/community.itexi:965: enharmoni
Dear Lilypond developers,
I read in the contributor's guide that there is a system of mentorship for
people who would like to help the project. Is that still the case? And if
so how do I get involved in it.
Kevin
___
lilypond-devel mailing list
lilypond
LGTM
https://codereview.appspot.com/187860043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello,
Here is the current patch countdown list. The next countdown will be on
December 11th.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=pa
Masamichi HOSODA writes:
>> I agree that changing the algorithms is preferred; I didn’t mean to
> suggest otherwise. But if that’s not going to happen overnight, and
> there is a way to mitigate the problem in the meantime without
> touching the code, the people affected would value it.
>
> I tr
> I agree that changing the algorithms is preferred; I didn’t mean to suggest
> otherwise. But if that’s not going to happen overnight, and there is a way
> to mitigate the problem in the meantime without touching the code, the people
> affected would value it.
I tried "-mfpmath=sse -msse2".
I
>> I've seen a proposed patch from Masamichi, but as David says, this may
>> fix the issue but doesn't shed any light on what is the root cause.
>> Is it worth trying to go back to an earlier version of gcc? If so,
>> how would I go about that?
>
> I lean towards just using Masamichi's patch.
I'
14 matches
Mail list logo
