Re: build errors
> I thought that make distclean would put my build tree in the same > state as it would be in a freshly cloned repository. Do `git status' to find out whether there are still additional files in your repository after `make distclean'. Of course, this doesn't show the files which are ignored by patterns in `.gitignore' files, and maybe exactly this is causing problems. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
build errors
Hi all, I'd appreciate any ideas you could give me about resolving a build error I have in my main lilypond build directory. I've done git reset --hard master make distclean ./autogen.sh make make doc I get the following error when I do make doc: /Users/Carl/lilypond/Documentation/out-www//rhythms.texi:1: Prev reference to nonexistent node `Pitches' (perhaps incorrect sectioning?). ./out-www/snippets.texi:64: Menu reference to nonexistent node `Pitches' (perhaps incorrect sectioning?). makeinfo: Removing output file `out-www/lilypond-snippets.info' due to errors; use --force to preserve. make[2]: *** [out-www/lilypond-snippets.info] Error 1 rm out-www/weblinks.itexi make[1]: *** [WWW-1] Error 2 make: *** [doc-stage-1] Error 2 If I create a new directory, and do a fresh clone of lilypond with lily-git.tcl, then do ./autogen.sh make make doc then everything runs successfully to completion. I thought that make distclean would put my build tree in the same state as it would be in a freshly cloned repository. Can anybody help me think of some ideas to test in order to find out what is causing the mix-up? Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: news item for new G clef?
On Fri, Apr 23, 2010 at 05:41:02PM -0600, Carl Sorensen wrote: > > On 4/23/10 5:28 PM, "Boris Shingarov" wrote: > > > On Sat, 24 Apr 2010 00:19:33 0100, Graham Percival wrote: > >> Entries in the Changes are completely up to individual > >> contributors. As a general rule, I'd say that when in doubt, add > >> an entry. > > I must have missed something -- I don't understand what you are > > discussing. Are you saying that when a contributor submits a patch, > > the patchset should include an update to the CHANGES file? > > Yes. No. :) > According to the Contributors' Guide, section 9.8.6 (under Adding or > modifying features) " An entry should be added to Documentation/changes.tely > to describe the feature changes to be implemented. This is especially > important for changes that change input file syntax." If you submit a patch that does something major, follow the above. If it doesn't change the input file syntax, and if you don't think it's major, then don't follow the above. In general, if you think people should be aware of a change, add something to Documentation/changes.tely. That this is *NOT* the same as the CHANGES file in the top source dir. (umm, if you have one... I'm not certain if that's still built automatically or not) Furthermore, I'm saying that if anybody thinks that some change is worth mentioning -- whether or not they authored that change themselves or not -- just go ahead and add it to changes.tely. Don't bother asking first. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: news item for new G clef?
On 4/23/10 5:28 PM, "Boris Shingarov" wrote: > > On Sat, 24 Apr 2010 00:19:33 0100, Graham Percival wrote: > On Sat, Apr 24, 2010 at 12:29:45AM 0200, Francisco Vila wrote: >>> 0ce6fe9 introduced a new 1,5 degrees rotated G clef, does this deserve >>> a news item? I think so. >> >> Entries in the Changes are completely up to individual >> contributors. As a general rule, I'd say that when in doubt, add >> an entry. > I must have missed something -- I don't understand what you are > discussing. Are you saying that when a contributor submits a patch, > the patchset should include an update to the CHANGES file? Yes. According to the Contributors' Guide, section 9.8.6 (under Adding or modifying features) " An entry should be added to Documentation/changes.tely to describe the feature changes to be implemented. This is especially important for changes that change input file syntax." Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: news item for new G clef?
I must have missed something -- I don't understand what you are discussing. Are you saying that when a contributor submits a patch, the patchset should include an update to the CHANGES file? On Sat, 24 Apr 2010 00:19:33 0100, Graham Percival wrote: On Sat, Apr 24, 2010 at 12:29:45AM 0200, Francisco Vila wrote: > > 0ce6fe9 introduced a new 1,5 degrees rotated G clef, does this deserve > > a news item? I think so. > > Entries in the Changes are completely up to individual > contributors. As a general rule, I'd say that when in doubt, add > an entry. > > Cheers, > - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: news item for new G clef?
On Sat, Apr 24, 2010 at 12:29:45AM +0200, Francisco Vila wrote: > 0ce6fe9 introduced a new 1,5 degrees rotated G clef, does this deserve > a news item? I think so. Entries in the Changes are completely up to individual contributors. As a general rule, I'd say that when in doubt, add an entry. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
news item for new G clef?
0ce6fe9 introduced a new 1,5 degrees rotated G clef, does this deserve a news item? I think so. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Change \cresc,\dim,\decresc to post-fix operators for (de)cresc spanners (issue956048)
LGTM. http://codereview.appspot.com/956048/diff/1/4 File python/convertrules.py (right): http://codereview.appspot.com/956048/diff/1/4#newcode3001 python/convertrules.py:3001: @rule ((2,13,19), (2, 13, 19) http://codereview.appspot.com/956048/show ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
