Il giorno gio 22 dic 2016 alle 18:48, Paul ha
scritto:
I gave it a try. Installation seemed to go fine, but then on booting
it up I get past the GRUB screen and then it goes to a black
unresponsive screen at "loading initial ramdisk..." Haven't had a
chance to troubleshoot it further. I'm a
LGTM
https://codereview.appspot.com/319880043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 22.12.2016 23:21, gra...@percival-music.ca wrote:
https://codereview.appspot.com/319880043/diff/1/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):
https://codereview.appspot.com/319880043/diff/1/Documentation/web/community.itexi#newcode434
Documentation
LGTM
https://codereview.appspot.com/311430043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM, and I'm happy with pushing it directly to staging.
https://codereview.appspot.com/312190043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
https://codereview.appspot.com/312210043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
https://codereview.appspot.com/319880043/diff/1/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):
https://codereview.appspot.com/319880043/diff/1/Documentation/web/community.itexi#newcode434
Documentation/web/community.itexi:434: every bug can be demonstrated in
f
>> One nit: Please avoid overlong lines in the source code; it should
>> be limited to 80 characters per line to improve legibility.
>
> Well, a number of lines are longer than 80 characters, but most are
> shorter than their predecessors. If the 80 character limit should
> be obeyed, it would b
Hello Paul
On 22/12/16 17:48, Paul wrote:
Hi Federico,
Thanks and congrats on the new release!
I gave it a try. Installation seemed to go fine, but then on booting
it up I get past the GRUB screen and then it goes to a black
unresponsive screen at "loading initial ramdisk..." Haven't had
> On 22 Dec 2016, at 18:20, Hans Aikema wrote:
>
>
>> On 22 Dec 2016, at 14:05, Masamichi Hosoda wrote:
>>
>> In my environments, autoconf does not raise such error.
>> Do you set the "set -u" or "set -o nounset" somewhere?
>> If so, would you remove the setting?
> The set -u
Hi Federico,
Thanks and congrats on the new release!
I gave it a try. Installation seemed to go fine, but then on booting it
up I get past the GRUB screen and then it goes to a black unresponsive
screen at "loading initial ramdisk..." Haven't had a chance to
troubleshoot it further. I'm at
Il giorno mer 7 dic 2016 alle 8:01, Graham Percival
ha scritto:
On Mon, Dec 05, 2016 at 06:03:28PM +, Carl Sorensen wrote:
On 12/5/16 10:28 AM, "lilypond-devel on behalf of Graham Percival"
wrote:
>The website *is* tied to the documentation. That decision was
>made in 2009, and the
> On 22 Dec 2016, at 14:05, Masamichi Hosoda wrote:
>
> In my environments, autoconf does not raise such error.
> Do you set the "set -u" or "set -o nounset" somewhere?
> If so, would you remove the setting?
The set -u (or to be complete set -ux) I discovered inside
/
On 2016-12-22 14:53, Knut Petersen wrote:
Hi Alexander et al.!
how about putting the patch on Rietveld?
I agree that this should go into a normal patch review process
now. Knut, are you familiar with the git cl proceedings? If not,
it’s explained in the CG 1.3 and 2.3.
+1. Let us know if you
Am 22.12.2016 um 15:00 schrieb Knut Petersen:
> Hi Werner!
>
>> One nit: Please avoid overlong lines in the source code; it should be
>> limited to 80 characters per line to improve legibility.
>>
>
> Well, a number of lines are longer than 80 characters, but most are
> shorter than
> their prede
Hi Werner!
One nit: Please avoid overlong lines in the source code; it should be
limited to 80 characters per line to improve legibility.
Well, a number of lines are longer than 80 characters, but most are shorter than
their predecessors. If the 80 character limit should be obeyed, it would b
Hi Alexander et al.!
how about putting the patch on Rietveld?
I agree that this should go into a normal patch review process now.
Knut, are you familiar with the git cl proceedings? If not, it’s
explained in the CG 1.3 and 2.3.
+1. Let us know if you need help. I went through the procedure ju
On 2016-12-21 17:05, tisimst wrote:
On Wed, Dec 21, 2016 at 5:22 AM, Alexander Kobel-2 [via Lilypond] <
ml-node+s1069038n198284...@n5.nabble.com> wrote:
On 2016-12-20 17:21, Abraham Lee wrote:
Maybe the question I really have is this: what does "given this
length _if possible_" mean and what go
On 2016-12-22 13:03, Simon Albrecht wrote:
On 22.12.2016 02:17, Thomas Morley wrote:
2016-12-22 1:33 GMT+01:00 Knut Petersen:
Hi everybody!
Attached find a new version of the patch.
Please test. Read the updated manuals.
Feel free to provide corrections and translations!
cu,
Knut
Hi Knut
In my environments, autoconf does not raise such error.
Do you set the "set -u" or "set -o nounset" somewhere?
If so, would you remove the setting?
>>> The set -u (or to be complete set -ux) I discovered inside
>>>
>>> /home/gub/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--li
Knut Petersen wrote Thursday, December 22, 2016 12:33 AM
> Attached find a new version of the patch.
> Please test. Read the updated manuals.
>
> Feel free to provide corrections and translations!
Looks promising. I have several comments to make, but it will be
much easier to do that when the
On 22.12.2016 02:17, Thomas Morley wrote:
2016-12-22 1:33 GMT+01:00 Knut Petersen:
Hi everybody!
Attached find a new version of the patch.
Please test. Read the updated manuals.
Feel free to provide corrections and translations!
cu,
Knut
Hi Knut,
how about putting the patch on Rietveld?
22 matches
Mail list logo
