- Original Message -
From: Pavel Roskin pro...@gnu.org
I'm not in a hurry at all. I'm not sure what needs to be sent. It's a
one word change after all.
--
Regards,
Pavel Roskin
Normally you'd send a patch, which would be applied to master and pushed.
Given that it's so
- Original Message -
From: Phil Holmes m...@philholmes.net
To: Pavel Roskin pro...@gnu.org
Cc: lilypond-devel@gnu.org
Sent: Saturday, February 18, 2012 10:56 AM
Subject: Re: recommend setting ragged-last-bottom to false
forlargescores(issue 5651077)
- Original Message -
Phil Holmes m...@philholmes.net writes:
Normally you'd send a patch, which would be applied to master and
^^
pushed. Given that it's so simple, as you say, I'll do this and push
to staging soon.
^^^
Pushed to staging as
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Saturday, February 18, 2012 11:31 AM
Subject: Re: recommend setting ragged-last-bottom to
falseforlargescores(issue 5651077)
Phil Holmes m...@philholmes.net writes:
Normally you'd send a patch,
Phil Holmes m...@philholmes.net writes:
I assume you're contrasting apply to master and push to staging.
I wasn't being exactly explicit, but I believe what I said was correct
- I take a patch, apply it to current master and then push the result
to staging.
That will only work in case of
- Original Message -
From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
Cc: lilypond-devel@gnu.org
Sent: Saturday, February 18, 2012 11:46 AM
Subject: Re: recommend setting ragged-last-bottom to
falseforlargescores(issue 5651077)
Phil Holmes m...@philholmes.net
Looks OK.
--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Looks excellent to me!
Makes Scheme engravers much more accessible.
Thanks,
Carl
http://codereview.appspot.com/5672085/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
See here:
http://lilypond.org/doc/v2.15/examples
This seems to me to be a hangover to the days when the web site didn't have
the nice examples on
http://lilypond.org/doc/v2.15/Documentation/web/examples. It seemed
complete in 2.12:
http://lilypond.org/doc/v2.12/examples
but now seems to
Reviewers: carl.d.sorensen_gmail.com,
Message:
On 2012/02/18 16:19:35, Carl wrote:
Looks excellent to me!
Makes Scheme engravers much more accessible.
Well, it is just syntactic sugar (or rather skimming). But it would
appear that working with quoting and quasiquoting and unquoting and
Phil, could you please put this patch to test again?
Thanks,
Julien
http://codereview.appspot.com/5494069/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
I'm relaunching my call for optimization, as the times of the patch are back up
to prohibitive level as I've added more and more grobs into the vertical
skyline calculation (notably flags, which add 3 seconds for every minute of
compile time). Obviously, the easy solution is to just pick and
- Original Message -
From: julien.ri...@gmail.com
To: m...@philholmes.net; paconet@gmail.com
Cc: lilypond-devel@gnu.org; re...@codereview-hr.appspotmail.com
Sent: Saturday, February 18, 2012 7:59 PM
Subject: Re: Build translated manuals: Don't rebuild everything each time
unless
13 matches
Mail list logo
