Reinhold Kainhofer reinh...@fam.tuwien.ac.at writes:
On 2012-02-02 18:11, Phil Holmes wrote:
- Original Message - From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
I believe James indicated his big machine was on 24x7 - hence my
instructions if he has some time to
David Kastrup d...@gnu.org writes:
Reinhold Kainhofer reinh...@fam.tuwien.ac.at writes:
On 2012-02-02 18:11, Phil Holmes wrote:
- Original Message - From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
I believe James indicated his big machine was on 24x7 - hence my
Hi,
in the list of critical issues the recent issue 2271
URL:http://code.google.com/p/lilypond/issues/detail?id=2271 is the
only one I see without an obvious path forward.
One serious option is ending the support for MacOSX 10.4. If you are a
user that would be affected by such a step, or a
2012/2/3 David Kastrup d...@gnu.org:
Since I just pushed about 4 patches (2 of them from me) and there has
been another translation merge (they tend to be prone to surprises in
particular when we have syntax changes),
Dear David: of course. What else do you expect?
I'd rather say: merging
Francisco Vila paconet@gmail.com writes:
2012/2/3 David Kastrup d...@gnu.org:
Since I just pushed about 4 patches (2 of them from me) and there has
been another translation merge (they tend to be prone to surprises in
particular when we have syntax changes),
Dear David: of course. What
2012/2/3 David Kastrup d...@gnu.org:
It looked like there were a lot of changes in Italian. And many of the
changes we actually had problems with were trivial. makeinfo does not
care much about the complexity of problems it complains about.
I meant trivial as in absolutely no problem giving
Francisco Vila paconet@gmail.com writes:
2012/2/3 David Kastrup d...@gnu.org:
It looked like there were a lot of changes in Italian. And many of the
changes we actually had problems with were trivial. makeinfo does not
care much about the complexity of problems it complains about.
I
Now that the Patchy staging-merge is running ok, it's time to
force the next issue:
I will not be making any more releases, stable or unstable,
as long as there are issues to verify relating to a
previously-released version.
At the time of this writing, this means that if *ANY* issue on
On Fri, Feb 03, 2012 at 11:56:06AM +0100, David Kastrup wrote:
in the list of critical issues the recent issue 2271
URL:http://code.google.com/p/lilypond/issues/detail?id=2271 is the
only one I see without an obvious path forward.
A quick glance at
On Fri, Feb 03, 2012 at 01:14:52PM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
At the time of this writing, this means that if *ANY* issue on this
list:
http://code.google.com/p/lilypond/issues/list?can=7
does *NOT* say fixed_2_15_28, there will be no
Graham Percival gra...@percival-music.ca writes:
On Fri, Feb 03, 2012 at 01:14:52PM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
At the time of this writing, this means that if *ANY* issue on this
list:
http://code.google.com/p/lilypond/issues/list?can=7
On Fri, Feb 03, 2012 at 02:14:41PM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Programmers gives things fixed_* tags.
You wish.
Heh. Normative vs. descriptive. :)
Cheers,
- Graham
___
lilypond-devel mailing
On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote:
Looks like Dave has marked all the outstanding fixes as verified while I was
busy testing 1416.
almost; there's still 2149.
My understanding is that they still all need to be tested. I'm travelling
from Saturday but I'll try to
Graham Percival gra...@percival-music.ca writes:
On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote:
Looks like Dave has marked all the outstanding fixes as verified
while I was busy testing 1416.
almost; there's still 2149.
You could have stowed the whip for a few minutes. There
On Fri, Feb 03, 2012 at 01:45:26PM +, Graham Percival wrote:
On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote:
My understanding is that they still all need to be tested. I'm travelling
from Saturday but I'll try to get through as many as I can between now and
then.
On 12-02-02 11:45 PM, m...@apollinemike.com wrote:
On Feb 3, 2012, at 6:14 AM, Colin Campbell wrote:
For 20:00 MST Sunday February 5th, 2012
Critical:
Issue 2267
http://code.google.com/p/lilypond/issues/detail?id=2267: Patch:
Gets left Hairpin bounds correct with tempo indications - R
Colin Hall colingh...@gmail.com writes:
On Fri, Feb 03, 2012 at 01:45:26PM +, Graham Percival wrote:
On Fri, Feb 03, 2012 at 01:40:49PM +, Colin Hall wrote:
My understanding is that they still all need to be tested. I'm
travelling from Saturday but I'll try to get through as many
To be honest, there are many things I don't understand. In fact, I
reduced the example to understand it better.
Why is horizontal spacing affected even though the purity affects the
Y-axis only? Why do stems fix the spacing? Why doesn't this cause the
spacing problem:
\override NoteHead
The regtest option-help.ly emits the help text for ly:set-option. The idea
is that the logfiles will thus be compared in the regtest checking. Only
problem is that the list seems to go to stdout and the logfiles are produced
from stderr, so no checking actually occurs, AFAICS. This has the
Phil Holmes em...@philholmes.net writes:
The regtest option-help.ly emits the help text for ly:set-option. The
idea is that the logfiles will thus be compared in the regtest
checking. Only problem is that the list seems to go to stdout and the
logfiles are produced from stderr, so no
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Friday, February 03, 2012 5:20 PM
Subject: Re: Another stderr/stdout question
Phil Holmes em...@philholmes.net writes:
The regtest option-help.ly emits the help text for ly:set-option. The
idea
Dear developers,
i hoped to rewrite Patchy to make it more robust, user-friendly and
solve problems that David experienced with his fix for 2240;
unfortunately it turned out that i'm not experienced enough to do
this. After 50 hours of struggle i'm so frustrated that i cannot
continue.
I'm sorry
2012/2/4 Janek Warchoł janek.lilyp...@gmail.com:
PS despite how this turned out, i'd like to thank Julien and Mike for
their help.
And, of course, Carl.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
23 matches
Mail list logo
