Updates:
Status: Verified
Comment #3 on issue 1736 by brownian.box: clarify description of minimal
examples
http://code.google.com/p/lilypond/issues/detail?id=1736
Fixed in 2.15.5, I guess. Verified.
___
bug-lilypond mailing list
bug
Updates:
Status: Fixed
Labels: -Patch-review
Comment #2 on issue 1736 by lemniska...@gmail.com: clarify description of
minimal examples
http://code.google.com/p/lilypond/issues/detail?id=1736
pushed with ID 402e3b1ac8d0c65b63a992dfd1247ed058e69ff8
Updates:
Owner: lemniska...@gmail.com
Comment #1 on issue 1736 by colinpkc...@gmail.com: clarify description of
minimal examples
http://code.google.com/p/lilypond/issues/detail?id=1736
This has had its countdown; please mark as fiuxed and quote the commit
message from the patch
Status: Started
Owner:
Labels: Type-Documentation Priority-Low Patch-review
New issue 1736 by lemniska...@gmail.com: clarify description of minimal
examples
http://code.google.com/p/lilypond/issues/detail?id=1736
http://codereview.appspot.com/4636082
On 7 Dec 2007, at 23:58, Graham Percival wrote:
There is nobody who knows more about the internals than me who has
the time to help out.
Perhaps you should, that is, having connections set up it makes it to
consult at need.
And I only spend about two hours a week on the bugs. There is a
(oops, I sent it too soon)
2007/12/7, Hans Aberg [EMAIL PROTECTED]:
Sure you have a lot experience with structure of LilyPond bugs, you
even describe that it several places. If you want to cut down on your
own time, drop off hints as you did to me first time: Is this or
that really
by his
comments on non-minimal examples. The next time you submit a bug report, I'm
sure you will spend a few more minutes yourself first. Apart from
simplifying the
task for Graham and the LilyPond hackers, another main advantage of this
exercise is that the process of reducing an example down
Valentin Villenave wrote:
2007/12/7, Hans Aberg [EMAIL PROTECTED]:
Sure you have a lot experience with structure of LilyPond bugs, you
even describe that it several places. If you want to cut down on your
own time, drop off hints as you did to me first time: Is this or
that really necessary?
On 7 Dec 2007, at 02:20, Graham Percival wrote:
Hans Aberg wrote:
When I made the first report, I had no idea what was causing it.
All I knew was that replacing the quadruplet with a rest made it
problem disappear, so it looked to me as though that was the
problem. You, with your broader
On 7 Dec 2007, at 12:20, Valentin Villenave wrote:
The point is: we do *not* have enough people to handle all this (so
this is a very different situation from other places you've been used
to). LilyPond is:
- a huge project
- a large community
- a very small development team, with only
time.
He said that he did not know much about the internals. So the
suggestion is to have somebody with that hekping out, which he
already noticed.
Please don't feel insulted by his
comments on non-minimal examples. The next time you submit a bug
report, I'm
sure you will spend a few
maintainers, whatever -- in lilypond.
Please don't feel insulted by his
comments on non-minimal examples. The next time you submit a bug
report, I'm
sure you will spend a few more minutes yourself first.
Don't you think folks might find it insulting, as you essentially do,
saying they should spend
Hans Aberg wrote:
When I made the first report, I had no idea what was causing it. All I
knew was that replacing the quadruplet with a rest made it problem
disappear, so it looked to me as though that was the problem. You, with
your broader knowledge of LilyPond bugs,
I wish that people
13 matches
Mail list logo
