"Phil Holmes" writes:
> Sorry, Marc. To do this completely, you will need to add the changed
> file to snippets/new. The files in snippets get over-written when we
> import from the LSR, so this update would be lost. However, to make
> current git compile, you do also need to keep this change
- Original Message -
From: "Marc Hohl"
To:
Sent: Saturday, July 28, 2012 7:07 PM
Subject: Re: Email from Phil's patchy
Am 28.07.2012 19:43, schrieb Marc Hohl:
Am 28.07.2012 15:27, schrieb David Kastrup:
"Phil Holmes" writes:
Ok, I'll be backing this out. If someone with horsepow
Am 28.07.2012 19:43, schrieb Marc Hohl:
Am 28.07.2012 15:27, schrieb David Kastrup:
"Phil Holmes" writes:
Ok, I'll be backing this out. If someone with horsepower can
produce a
relevant log file for the problem (possibly the one listed above is
still around which might be a good start), thi
Am 28.07.2012 15:27, schrieb David Kastrup:
"Phil Holmes" writes:
Ok, I'll be backing this out. If someone with horsepower can produce a
relevant log file for the problem (possibly the one listed above is
still around which might be a good start), this would likely be quite
helpful.
--
David
On Fri, Jul 20, 2012 at 10:40 PM, David Kastrup wrote:
>
> Hello,
>
> before further delaying the announcement due to minor issues (for
> example, OpenStreetMap wants to have the meeting occur in an electrical
> power transformer array), here is the web site with the information.
> I'll add forgot
"Phil Holmes" writes:
>> Ok, I'll be backing this out. If someone with horsepower can produce a
>> relevant log file for the problem (possibly the one listed above is
>> still around which might be a good start), this would likely be quite
>> helpful.
>>
>> --
>> David Kastrup
>
> Parsing...
>
- Original Message -
From: "David Kastrup"
To:
Sent: Saturday, July 28, 2012 1:41 PM
Subject: Re: Email from Phil's patchy
philehol...@googlemail.com writes:
12:31:10 (UTC) Begin LilyPond compile, previous commit at
3573a92d92728dc8d6452e5cd3cfba73e49e6990
12:31:28 Merged staging,
philehol...@googlemail.com writes:
> 12:31:10 (UTC) Begin LilyPond compile, previous commit at
> 3573a92d92728dc8d6452e5cd3cfba73e49e6990
>
> 12:31:28 Merged staging, now at:
> 65c53165ab3535a9186f501c9a8b454d07c82642
>
> 12:31:29 Success:./autogen.sh --noconfigure
>
> 12:31:4
12:31:10 (UTC) Begin LilyPond compile, previous commit at
3573a92d92728dc8d6452e5cd3cfba73e49e6990
12:31:28 Merged staging, now at:65c53165ab3535a9186f501c9a8b454d07c82642
12:31:29Success:./autogen.sh --noconfigure
12:31:42Success:..
lilypond-a...@mandereau.net writes:
> 10:35:12 (UTC) Begin LilyPond compile, previous commit at
> d459b17897c0218450bfb0bab6403c16705bd17a
>
> 10:35:14 Merged staging, now at:
> 65c53165ab3535a9186f501c9a8b454d07c82642
>
> 10:35:17 Success:./autogen.sh --noconfigure
>
> 10:35:
10:35:12 (UTC) Begin LilyPond compile, previous commit at
d459b17897c0218450bfb0bab6403c16705bd17a
10:35:14 Merged staging, now at:65c53165ab3535a9186f501c9a8b454d07c82642
10:35:17Success:./autogen.sh --noconfigure
10:35:50Success:..
http://codereview.appspot.com/6447052/diff/1/scm/markup.scm
File scm/markup.scm (right):
http://codereview.appspot.com/6447052/diff/1/scm/markup.scm#newcode82
scm/markup.scm:82: (define-public (markup->string props m)
This changes the interface of a public function in an incompatible
manner.
Th
http://codereview.appspot.com/6441058/diff/1/lily/parser.yy
File lily/parser.yy (right):
http://codereview.appspot.com/6441058/diff/1/lily/parser.yy#newcode993
lily/parser.yy:993: /* Copy the new header fields, i.e. overwrite
existing, but preserve unchanged ones */
The problem with this approac
Colin Campbell writes:
> On 12-07-27 10:25 PM, Werner LEMBERG wrote:
>>> It did not accept your key. Sure you uploaded the _public_ key to
>>> Savannah and it got accepted?
>> Be careful of newlines accidentally inserted in the public key while
>> entering it in the web interface!
>>
>>
>>
>> Yes: cis, ces, fisis, feses, etc.
>
> And asas.
Yes, I think so.
> Or aeses? Or was that ases?
Never heard.
> bes or heses?
Rather the latter.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/lis
Werner LEMBERG writes:
>>> At least for German, the current syntax is the only good one IMHO,
>>> both for accidentals (for the twelve tones of an octave
>>
>> You mean the 35 tones. After all, we are talking printed output and
>> not Midi.
>
> Yes: cis, ces, fisis, feses, etc.
And asas. Or a
16 matches
Mail list logo