Hi,
the default chord repeat code contains stuff like
;; If previous-chord has an length property, then it means that it
;; has been processed by a music iterator. In other words, the chord
;; has been memorized from an other music block, which is certainly not
;; what the user has
On 2012/01/25 22:37:20, mail_philholmes.net wrote:
As a Brit, I would write it slightly less definitively. Please allow
a few
days.
I probably shouldn't have found that as funny as I did. :)
I still don't like that, though. As a user, when I report a bug, I want
to know that it's been
Well, here is what I can think off my head.
a) feature freeze. Nothing added that requires documentation changes.
b) get rid of all critical issues
c) release candidate(s)
d) proofread the docs for obvious mistakes
e) make sure all appropriate regtests are there
f) update the snippets for
On Thu, Jan 26, 2012 at 12:33:31PM +0100, David Kastrup wrote:
a) feature freeze. Nothing added that requires documentation changes.
why bother? the two-week release candidate takes care of this.
b) get rid of all critical issues
yes
c) release candidate(s)
yes
d) proofread the docs
2012/1/26 David Kastrup d...@gnu.org:
As far as I can see, the snippet _code_ is not subject to translation
issues,
Right. Just make sure any _needed_ (backwards-incompatible) change in
code is made in translations as well.
so e) can be pretty much done in parallel. Translation work
2012/1/26 Graham Percival gra...@percival-music.ca:
g) get the translations up to par where there are translation workers
no,
Yes
we've never bothered with that in the past,
_we_ have actuall bothered.
and this would
push the release back to 2013 or later
Don't underestimate us. Say
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
The problem here is that lilypond builds up memory from 400MB
A potentially silly question: does make doc include running regtests?
(i don't mean regtest comparison, just compiling all the snippets)
I don't see anything about it in CG.
thanks,
Janek
___
lilypond-devel mailing list
lilypond-devel@gnu.org
2012/1/26 Janek Warchoł janek.lilyp...@gmail.com:
A potentially silly question: does make doc include running regtests?
(i don't mean regtest comparison, just compiling all the snippets)
I don't see anything about it in CG.
Yes.
Cheers,
Neil
___
- Original Message -
From: Neil Puttock n.putt...@gmail.com
To: Janek Warchoł janek.lilyp...@gmail.com
Cc: LilyPond Developmet Team lilypond-devel@gnu.org
Sent: Thursday, January 26, 2012 5:00 PM
Subject: Re: silly question: does make doc include running regtests?
2012/1/26 Janek
- Original Message -
From: Reinhold Kainhofer reinh...@kainhofer.com
To: Julien Rioux jri...@physics.utoronto.ca
Cc: lilypond-devel@gnu.org; bug-lilyp...@gnu.org
Sent: Thursday, January 26, 2012 4:13 PM
Subject: Re: make doc problem
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks,
Le 26 janv. 2012 à 11:00, David Kastrup a écrit :
The bad news is that absolute pitch friends would have to call the \q
function (any better name for it?) explicitly. Since q is an input
convenience, and relative pitch is also an input convenience, I don't
think that there would be much of
Pavel, I pushed for you.
author Pavel Roskin pro...@gnu.org
Thu, 26 Jan 2012 21:17:13 + (21:17 +)
committer James Lowe pkx1...@gmail.com
Thu, 26 Jan 2012 21:19:06 + (21:19 +)
commit 224246365f67fb44799fee4eb00e5debea5a35ec
Can you close this issue here?
James
Pavel, I pushed this for you
author Pavel Roskin pro...@gnu.org
Thu, 26 Jan 2012 21:22:32 + (21:22 +)
committer James Lowe pkx1...@gmail.com
Thu, 26 Jan 2012 21:22:32 + (21:22 +)
commit 05efb98f2e3ff68f4bb8221db640b0174bfcde93
Please close this issue. Thanks.
James
Nicolas Sceaux nicolas.sce...@gmail.com writes:
Le 26 janv. 2012 à 11:00, David Kastrup a écrit :
The bad news is that absolute pitch friends would have to call the \q
function (any better name for it?) explicitly. Since q is an input
convenience, and relative pitch is also an input
Hi,
i think the output of beam-shortened-lengths.ly doesn't look good, see
in current regtests
http://www.lilypond.org/doc/v2.15/input/regression/collated-files.html
. Am i missing something?
cheers,
Janek
___
lilypond-devel mailing list
Janek Warchol janek.lilyp...@gmail.com wrote in message
news:CANYDDppbpzXAeepYCZ24rpu+RVQm21gO9beMCw357jxj_w=g...@mail.gmail.com...
Hi,
i think the output of beam-shortened-lengths.ly doesn't look good, see
in current regtests
On 22/01/2012 2:58 PM, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the build.
Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
Could we redistribute the regression test input files into
On 26/01/2012 11:13 AM, Reinhold Kainhofer wrote:
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
The problem
On Thu, Jan 26, 2012 at 05:57:43PM -0500, Julien Rioux wrote:
On 22/01/2012 2:58 PM, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the build.
Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
On 26/01/2012 6:14 PM, Graham Percival wrote:
On Thu, Jan 26, 2012 at 05:57:43PM -0500, Julien Rioux wrote:
On 22/01/2012 2:58 PM, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the build.
Disk access and usage of swap when compiling
On 2012-01-27 00:00, Julien Rioux wrote:
On 26/01/2012 11:13 AM, Reinhold Kainhofer wrote:
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down
There are no issues for review today, other than David's #2247, which
has already been pushed, but he is leaving it up for a few days, just in
case.
Cheers,
Colin
--
I've learned that you shouldn't go through life with a catcher's mitt on both
hands.
You need to be able to throw something
Phil Holmes mail at philholmes.net writes:
i think the output of beam-shortened-lengths.ly doesn't look good
What exactly is the problem?
The self-description says the up-pointing stems should be shortened,
but they are not. We didn't see it in real music because the bug
depends on the
24 matches
Mail list logo
