On Sat, Oct 29, 2011 at 08:30:07PM +0200, m...@apollinemike.com wrote:
> On Oct 29, 2011, at 6:01 PM, Graham Percival wrote:
>
> > 2) I don't have a fast enough computer to want to sit through a
> > doc rebuild for every patch
>
> I may be able to get a dedicated server for Patchy in the next yea
On Oct 29, 2011, at 6:01 PM, Graham Percival wrote:
>
> 2) I don't have a fast enough computer to want to sit through a
> doc rebuild for every patch
>
I may be able to get a dedicated server for Patchy in the next year or so -
I'll keep you posted.
Cheers,
MS
__
On Sat, Oct 29, 2011 at 03:38:27PM +0200, m...@apollinemike.com wrote:
> I'll have time in early 2012 to work on Patchy in more detail,
> but there is one contribution that I can make right away. I
> thought that patchy did a full doc build (BUILD_ALL_DOCS =
> True), but the most recent problem wi
"m...@apollinemike.com" writes:
> On Oct 27, 2011, at 11:55 AM, Graham Percival wrote:
>
>> Again, it would be great if somebody with more patience and/or
>> pride in their work could take over Patchy. As an incentive, you
>> don't need to deal with our review process. I'll hand git push
>> abi
On Oct 27, 2011, at 11:55 AM, Graham Percival wrote:
> Again, it would be great if somebody with more patience and/or
> pride in their work could take over Patchy. As an incentive, you
> don't need to deal with our review process. I'll hand git push
> ability for that repo out to anybody; just h
In order to de-mystify Patchy, I'm going to point people at the
source:
https://github.com/gperciva/lilypond-extra/blob/master/patches/compile_lilypond_test.py
As you can see, it's pretty ugly python, but it works. Or at
least, the testing-patches parts work. I haven't checked
dev/staging since
