Re: Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-03-09 Thread lilypond
Updates: Status: Verified Comment #11 on issue 2333 by julien.r...@gmail.com: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333 The new regular expression is part of the source tree as checked out from current git release/unstable

Re: Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-03-05 Thread lilypond
Updates: Status: Fixed Labels: -Patch-push Fixed_2_15_33 Comment #10 on issue 2333 by philehol...@gmail.com: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333 Pushed to staging as fe2e679d876eba72077a9ced1b918ad330e79bb4 _

Re: Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-03-04 Thread lilypond
Comment #9 on issue 2333 by philehol...@gmail.com: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333 I'd like to get this pushed to get rid of a few messages in make doc. Reinhold - could you push, please? I'll do it in a few days if no

Re: Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-02-23 Thread lilypond
Updates: Owner: reinhold...@gmail.com Comment #8 on issue 2333 by colinpkc...@gmail.com: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333 (No comment was entered for this change.) ___ b

Re: Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-02-21 Thread lilypond
Updates: Labels: -Patch-countdown Patch-push Comment #7 on issue 2333 by colinpkc...@gmail.com: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333 Counted down to 20120221, please push. _

Re: Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-02-19 Thread lilypond
Comment #5 on issue 2333 by reinhold...@gmail.com: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333 The purpose of this patch is to prevent some warnings about missing include files while building the documentation (in particular the tra

Re: Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-02-19 Thread lilypond
Comment #4 on issue 2333 by d...@gnu.org: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333 Well, I did not mean "regtests" as much as "make check". But of course "make check" does not involve "make doc": I confused this with the opera

Re: Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-02-19 Thread lilypond
Comment #3 on issue 2333 by philehol...@gmail.com: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333 I see no reason why it should affect regtests - simply the text sent to terminal with a make doc.

Re: Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-02-19 Thread lilypond
Updates: Labels: Patch-review Comment #2 on issue 2333 by d...@gnu.org: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333#c2 Patchy the autobot says: LGTM. Was this expected to _not_ change regtests? Should this be tested once a

Re: Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-02-18 Thread lilypond
Updates: Labels: Patch-new Comment #1 on issue 2333 by reinhold...@gmail.com: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333 Fix 2333: extract_texi_filenames.py should only look at includes if they are not commented out Simpl

Issue 2333 in lilypond: extract-texi-filenames doesn't ignore comments

2012-02-18 Thread lilypond
Status: Accepted Owner: Labels: Type-Build Warning New issue 2333 by philehol...@gmail.com: extract-texi-filenames doesn't ignore comments http://code.google.com/p/lilypond/issues/detail?id=2333 Create a test.texi file with this line: @c @include learning/preface.itely My understanding