Got it. Then, here is the state of things:
1/6 Bug is first reported on the bug list. 1/7 Neil reports adding a default 'extra-spacing-height to key signature. 1/10 Keith confirms that this works and that he gets a clean make check. 1/13 Phil holmes reports the regression on the bugtracker (2.13.46). Graham identifies that the output was correct on the bugtracker (2.12.3). 1/19 Mike confirms that the regression is indeed due to 1190 and realizes that he is not subscribed to the bug list. Mike proposes a patch based on the discussion between Neil and Keith, which is attached to this e-mail and on Rietveld @ http://codereview.appspot.com/4031042.
0001-Fix-for-issue-1472.patch
Description: Binary data
Make check passes. Cheers, MS On Jan 19, 2011, at 5:23 PM, Carl Sorensen wrote: > On 1/19/11 2:51 PM, "m...@apollinemike.com" <m...@apollinemike.com> wrote: > >> Graham et all, >> >> I have read all of the postings and am up to date - I meant "what next" as a >> general question to the community in the sense of "would anyone who was >> actually involved in the pushing of this commit (Joe - I see your name >> associated with it - how much work did you do on it?) like to give me some >> guidance as to where to go so that I can find that which ultimately causes >> this regression?" In terms of man hours, I think that a little time invested >> by the people who were involved in producing the commit would be more >> efficient than my learning how lilypond functioned back when this was pushed. >> That said, if the response is "I have no clue," then I will get to figuring >> it >> out. > > I think the best "what next" response is for you to summarize the discussion > you have found on -bug, -devel, -user, and the issues comments to see what > you think the current proposed resolution is, if anything. > > There's been enough different discussion going on about this that I'm not > clear what has been said or proposed (that's why I asked about 1474). We > may have a solution already at hand, but I'm not up on it. > > The "shepherd" job is not to solve the bug, it's to make sure the developer > community is on the same page about the bug. > > Thanks, > > Carl > >
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel