Am 29.07.2012 11:16, schrieb David Kastrup:
Marc Hohl writes:
Am 29.07.2012 10:10, schrieb David Kastrup:
Now it is true that we probably did not have a formal discussion of
this in any rate, and you are probably quite keeping with some sort
of de-facto standard and are in the unlucky positi
Marc Hohl writes:
> Am 29.07.2012 10:10, schrieb David Kastrup:
>
>> Now it is true that we probably did not have a formal discussion of
>> this in any rate, and you are probably quite keeping with some sort
>> of de-facto standard and are in the unlucky position of standing next
>> when I am wak
Am 29.07.2012 10:10, schrieb David Kastrup:
Marc Hohl writes:
Am 29.07.2012 08:12, schrieb David Kastrup:
"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, s
Marc Hohl writes:
> Am 29.07.2012 08:12, schrieb David Kastrup:
>> "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.
Am 29.07.2012 08:12, schrieb David Kastrup:
"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
"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 back
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
"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
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:..
13 matches
Mail list logo