У ср, 2010-03-31 у 02:05 -0400, Boris Shingarov пише: > Hi Graham, > > > If you send a minimal example to this list, and no developer > > responds within a few days to begin discussing a patch, then I > > would expect somebody to add it to the tracker. I'm not certain > > if that has always happened, though. > > So in other words, not all bugs have bug reports in the tracker? > If the discussion takes a technical turn from the very beginning, > then we just discuss the patch through into the codebase, but > no trail in the tracker remains? Hi, Boris!
As one of persons who ideally should track all these discussions and submit proper bugreports, i can say that i can not decide in every case where it is a bug and where it is not. But if you can provide a minimal example, it will be easier. See also: http://lilypond.org/doc/v2.13/Documentation/web/bug-reports I understand that probably not every case may be illustrated by minimal example --- that is the difficulty for Bug Squad and for developers, i guess. ps. In this particular case --- i read every post, i assume there can be a bug somewhere, but for me --- it's hard to say *what* is a bug, *where* is it. You say: "Lyrics break estimation of vertical spacing" --- so, no-lyrics.ly should contain no "unwanted" vertical space? But it does, with 2.13.16. Or i've missed something? Next, i've commented out everything in \paper {} block (left paper-size alone) and problem disappeared. So, how this bug should be titled? "Lyrics... breaks.. *if* <some other conditions>" or like that? I'd *love* to submit a bugreport :O) But i can not, sorry :-( pps. "Melody" in your example can be minimized to \repeat "unfold" 392 { f e } It's quote good for minimal example, i believe. Thank You! > Hmm. I'd find it useful if we documented and kept trail of all > bugs in the tracker. You know, putting tags on pushes in the > form "fix for bug #XYZ", or if someone asks "what does this > code do" you can reply "see bug #XYZ", that kind of stuff. -- Dmytro O. Redchuk _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
