Re: lybook-db etc etc.

Graham Percival writes: > On Thu, Oct 27, 2011 at 07:25:19AM +0200, David Kastrup wrote: >> Graham Percival writes: >> >> > On Wed, Oct 26, 2011 at 05:13:56PM +0200, David Kastrup wrote: >> >> >> >> In my opinion, the whole lybook-db stuff needs to go. Instead, Lilypond >> >> is run _once_ fo

Re: lybook-db etc etc.

Am 2011-10-26 17:13, schrieb David Kastrup: Well, I am currently in the process of running make info (similar to make doc), and this is totally silly. In my opinion, the whole lybook-db stuff needs to go. Instead, Lilypond is run _once_ for all snippets of a lybook source, Lilypond is current

Re: Bisection/merge commits

David Kastrup writes: > I think adding --preserve-merges should help. The alternative is > --no-ff which refuses to do anything if master has separate commits. P.S.: After thinking about it, I decided I don't want to try to fix this part of the history. If my playing around with dev/staging is

Re: lybook-db etc etc.

Reinhold Kainhofer writes: > Am 2011-10-26 17:13, schrieb David Kastrup: >> Well, I am currently in the process of running make info (similar to >> make doc), and this is totally silly. >> >> In my opinion, the whole lybook-db stuff needs to go. Instead, Lilypond >> is run _once_ for all snippet

Re: the latest convert-ly fiasco

On Tue, Oct 25, 2011 at 07:02:48AM -0600, Colin Campbell wrote: > In the interests of 'get it done and make the paper work agree', > would you and Graham let me know which issues/patches are going > through slightly different channels? To be honest, I have no clue. > I gather that most or all of

Re: Bisection/merge commits

On Thu, Oct 27, 2011 at 09:14:10AM +0200, David Kastrup wrote: > P.S.: After thinking about it, I decided I don't want to try to fix this > part of the history. +1. It's just too risky to mess with git. > In future, rebase using --preserve-merges, and sorry for not noticing > this earlier. will

Re: Fixes slope errors from incorrect X extents in Beam::print. (issue 5293060)

On Oct 26, 2011, at 9:41 PM, k-ohara5...@oco.net wrote: > On Wed, 26 Oct 2011 11:40:27 -0700, m...@apollinemike.com > wrote: > >> What needs comments? > > Description of the different setup of the three instances of > Beam_scoring_problem, and their goals. > Done >> -) the x-span of the Beam

Re: Fixes slope errors from incorrect X extents in Beam::print. (issue 5293060)

On Oct 26, 2011, at 10:13 PM, carl.d.soren...@gmail.com wrote: > I don't understand beam-quanting well enough to evaluate most of the > code, but I've seen some concerns in properties and regtests. > > Thanks, > > Carl > > Carl, In general, you're absolutely right about the regtests. I've s

source for Patchy the autobot

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

Re: the latest convert-ly fiasco

Graham Percival writes: > On Tue, Oct 25, 2011 at 07:02:48AM -0600, Colin Campbell wrote: >> In the interests of 'get it done and make the paper work agree', >> would you and Graham let me know which issues/patches are going >> through slightly different channels? > > To be honest, I have no clue

Re: the latest convert-ly fiasco

On Thu, Oct 27, 2011 at 01:04:21PM +0200, David Kastrup wrote: > Uh, Graham? I think we need a version number bump. argh, apparently I forgot the "post-release steps" for 2.15.15. I'm not a university right now, so that'll have to wait until after midnight. sorry. - Graham

Re: lybook-db etc etc.

If you can do without lybookdb, it would be a more robust although less scalable design. I am not sure how intricate batching all of the png/pdf/eps generation is, we should probably decide after seeing the code that implements it. Lilypond being dominated by eps/png/pdf generation, and EPS/PDF g

PATCH: Countdown to 20111030

For 21:00 MDT Sunday October 30. Issue 1993 : Updates to bagpipe.ly - R 5307059 Issue 814 : warning-as-error should be enabled when compi

Re: Fixes slope errors from incorrect X extents in Beam::print. (issue 5293060)

On Thu, 27 Oct 2011 01:34:00 -0700, m...@apollinemike.com wrote: What about the x_span_ of the Beam_scoring_problem ? It represents two things at two different stages of Beam_scoring_problem. Too bad you didn't use two different variables. Starting at update_x_span_after_extremal_hangove

issues to verify

Dmytro, I see 40 issues to verify. Some of them are for 2.15.15, which is ok since it's only been 3 days since that went up, but I also see a bunch for 2.15.14 and 2.15.13. It's your job to either: 1. make the bug squad do their job, 2. do their job for them, or 3. ask for more help We ca