Re: Issue 1273 in lilypond: Woodwind Diagrams lead toGhostscripterror in latest git
"Trevor Daniels" writes: > Phil Holmes wrote Sunday, September 26, 2010 6:26 PM > > >> - Original Message - >> From: "Trevor Daniels" >> >>> BTW, please don't reply to messages in newsgroups. >>> I don't subscribe to any and that makes them very >>> messy for me to reply to. >> >> >> Tricky. I _only_ use a newsreader for bugs and devel and so can't >> reply by mail to send it to the group and the original poster. > > Well, I had to copy out the message and reenter > appropriate email addresses to reply to yours. > Can't you do the same? With Emacs, it is a matter of doing C-c C-t after F . The followup will then be both sent to the nntp server as well as to the poster, marked as a "courtesy copy". -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1273 in lilypond: Woodwind Diagrams lead toGhostscripterror in latest git
Phil Holmes wrote Sunday, September 26, 2010 6:26 PM - Original Message - From: "Trevor Daniels" BTW, please don't reply to messages in newsgroups. I don't subscribe to any and that makes them very messy for me to reply to. Tricky. I _only_ use a newsreader for bugs and devel and so can't reply by mail to send it to the group and the original poster. Well, I had to copy out the message and reenter appropriate email addresses to reply to yours. Can't you do the same? Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1273 in lilypond: Woodwind Diagrams lead toGhostscripterror in latest git
- Original Message - From: "Trevor Daniels" [snip] Trevor BTW, please don't reply to messages in newsgroups. I don't subscribe to any and that makes them very messy for me to reply to. Tricky. I _only_ use a newsreader for bugs and devel and so can't reply by mail to send it to the group and the original poster. -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Fw: Issue 1273 in lilypond: Woodwind Diagrams lead toGhostscripterror in latest git
Phil Holmes wrote" wrote in message news:i7ntha$vm...@dough.gmane.org... "Trevor Daniels" wrote in message news:f867cc5a71fc42b7b9f90fbb44692...@trevorlaptop... Carl Sorensen wrote Sunday, September 26, 2010 1:51 PM On 9/26/10 3:14 AM, "Trevor Daniels" wrote: Carl wrote Also, please note that we don't file bugs on any versions not yet released, because there really isn't a 2.13.35 yet. Why not? A bug which happened to have been noticed in a version compiled from git might have existed for some time. We don't expect the Bug Squad to do this research, do we? We expect the Bug Squad to test on the latest development release. OK. I see one of the actions for a Bug Squad member is to generate a png file demonstrating the problem. This clearly would demonstrate whether a problem which happened to be noticed in a git build was present in the latest GUB release. So I was wrong - we _do_ expect them to do this research. Presumably they should forward the report to -dev if the bug does not show in the latest GUB release. The original report said "does not work with lates git Lilypond 2.13.35 but works on 2.13.34-1". So my interpretation of this is that there is no bug on any release that most Bug Squad members could test to or generate output from. Yes, that's fine. I wasn't concerned with this particular issue, which was quite clear, but with the general procedure to deal with the case when a bug is reported on -bug which has been observed in a git build. This case is not covered explicitly in the CG. It seems it should either be forwarded to -dev or made the subject of a new issue depending on whether or not the bug manifests itself in the latest GUB build. Checking that and carrying out the appropriate action is a Bug Squad responsibility. Trevor BTW, please don't reply to messages in newsgroups. I don't subscribe to any and that makes them very messy for me to reply to. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
