On 12-05-14 07:13 AM, Joseph Rushton Wakeling wrote:
Might be a nice moment to see what I can do about that long-dormant
doc work. :-)
___
Let me know if I can help, Joseph, and welcome back!
Colin "the older one" Campbell
--
I've learned that y
Graham Percival writes:
> Tomorrow I'll go see the "science and technology" museum (maybe 4
> hours?),
4 weeks is more realistic.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypon
On Mon, May 14, 2012 at 01:48:54PM +0200, Joseph Rushton Wakeling wrote:
> On 14/05/12 11:41, David Kastrup wrote:
> >
>
> Before saying anything more, I'm sorry if my earlier email was
> offensive or intemperate; it wasn't meant to be.
Ditto.
> I was writing out of concern for the ease of contr
Joseph Rushton Wakeling writes:
> One of the frustrations on that occasion a year ago was that I would
> have been quite likely on my own initiative to see if I could do
> anything, _if_ I hadn't been treated to the lecture.
It is a reasonably safe guess that the "lecture" had been by Graham.
Gr
On 14/05/12 14:15, David Kastrup wrote:
They are treated by the bug squad picking up the suggestion and filing
it in the issue problem.
If someone suggested to you that they will refuse doing that, that
someone was not giving you correct information.
OK. :-)
To be fair, reconsidering things,
Joseph Rushton Wakeling writes:
> It's not trivial if I have to install custom code in order to submit a
> tiny doc patch!
>
> If I were hacking on LP itself then it would surely be a small issue
> by comparison, but I wasn't, and I don't think small tweak-y
> contributions should be treated this
On 14/05/12 11:41, David Kastrup wrote:
Before saying anything more, I'm sorry if my earlier email was offensive or
intemperate; it wasn't meant to be. I was writing out of concern for the ease
of contributing to LilyPond (more on that in a moment).
Have you actually used Rietveld for re
Joseph Rushton Wakeling writes:
> On 14/05/12 09:46, David Kastrup wrote:
>> We don't have a canonical developer, one whose personal
>> branch/repository would be official for the project.
>
> GitHub and Launchpad both permit branches to be owned by groups as
> well as individuals. I'm sure othe
On 14/05/12 09:46, David Kastrup wrote:
We don't have a canonical developer, one whose personal
branch/repository would be official for the project.
GitHub and Launchpad both permit branches to be owned by groups as well as
individuals. I'm sure other DVCS-based code hosts do as well, but tho
Joseph Rushton Wakeling writes:
> On 14/05/12 07:35, Graham Percival wrote:
>> On Mon, May 14, 2012 at 03:38:54AM +0200, Joseph Rushton Wakeling wrote:
>>> Here you go. :-) Let me know if it needs tweaking or might be
>>> better in another section of the guide.
>>
>> Please see the "summary for
On 14/05/12 07:35, Graham Percival wrote:
On Mon, May 14, 2012 at 03:38:54AM +0200, Joseph Rushton Wakeling wrote:
Here you go. :-) Let me know if it needs tweaking or might be
better in another section of the guide.
Please see the "summary for experienced developers" in the CG.
That really
On Mon, May 14, 2012 at 03:38:54AM +0200, Joseph Rushton Wakeling wrote:
> Here you go. :-) Let me know if it needs tweaking or might be
> better in another section of the guide.
Please see the "summary for experienced developers" in the CG.
- Graham
On 12/05/12 17:22, James wrote:
On 12 May 2012 14:24, Joseph Rushton Wakeling
A small word to this effect might be a nice addition to the contributor
guide (I'll make a patch if you like).
Sure go ahead.
Here you go. :-) Let me know if it needs tweaking or might be better in another
sectio
hello,
On 12 May 2012 14:24, Joseph Rushton Wakeling
wrote:
> On 12/05/12 14:29, James wrote:
>>
>> Assuming you are building from current master then make doc does
>> compile as all new checkins go to staging tree first and sit there
>> while a script runs (as it happens on my computer) that com
On Sat, May 12, 2012 at 01:56:33PM +0200, Joseph Rushton Wakeling wrote:
> On 12/05/12 13:37, David Kastrup wrote:
> >and that does not quite work. It would appear that the error handling
> >for a missing texi2html script is totally awful. I'd install texi2html
> >and rerun configure.
>
> Texi2h
On 12/05/12 14:29, James wrote:
Assuming you are building from current master then make doc does
compile as all new checkins go to staging tree first and sit there
while a script runs (as it happens on my computer) that compiles
staging through all the tests and if it passes them all (and that
in
Joseph,
On 12 May 2012 12:56, Joseph Rushton Wakeling
wrote:
> On 12/05/12 13:37, David Kastrup wrote:
>>
>> You are running a command
>>
>> - echo texi2html not found
>>
>> and that does not quite work. It would appear that the error handling
>> for a missing texi2html script is totally awf
On 12/05/12 13:37, David Kastrup wrote:
You are running a command
- echo texi2html not found
and that does not quite work. It would appear that the error handling
for a missing texi2html script is totally awful. I'd install texi2html
and rerun configure.
Texi2html was already installed
Joseph Rushton Wakeling writes:
> /home/joseph/code/lily/build/scripts/build/out/run-and-check
> "DEPTH=../../.. AJAX_SEARCH= TOP_SRC_DIR=/home/joseph/code/lily
> PERL_UNICODE=SD - echo texi2html not found --error-limit=0
[...]
> The logfile reads:
>
>build/scripts/build/out/run-and-check:
On 12/05/12 11:59, Phil Holmes wrote:
The doc build now issues far less "chatter" than it used to. With a single core
machine, it could well go an hour without a single message. If it's using CPU
and taking memory, be patient. If there's no response after a day, let us know.
OK, cool. It's nic
- Original Message -
From: "Joseph Rushton Wakeling"
To:
Sent: Saturday, May 12, 2012 8:37 AM
Subject: Doc build hanging (with memory leak?)
Hello all,
I've successfully build Lilypond itself from source, but when I try to
make doc, the build hangs on the first file
Hello all,
I've successfully build Lilypond itself from source, but when I try to make doc,
the build hangs on the first file it attempts to compile:
make[3]: Entering directory `/home/joseph/code/lily/build/input/regression'
LILYPOND_VERSION=2.15.39 /usr/bin/python
/home/joseph/code/lily/scr
22 matches
Mail list logo
