On Tue, Aug 02, 2011 at 07:22:33AM +0100, m...@apollinemike.com wrote:
> On Aug 2, 2011, at 6:22 AM, Graham Percival wrote:
>
> >* any segfault, regardless of what the input file looks like
> > or which options are given.
>
> I like the first one, but I think the second needs to be tweak
On Aug 2, 2011, at 6:22 AM, Graham Percival wrote:
> ** Proposal details
>
> Priority-critical:
>
>* a reproducible failure to build either make or make doc,
> from an empty build tree, in a first run, if configure does
> not report any errors.
>* any segfault, regardless of wh
I'm expecting a moderate amount of discussion for this one.
http://lilypond.org/~graham/gop/gop_8.html
** Proposal summary
At the moment, a stable release is entirely dependent on the
number of Critical issues, but there’s some questions about
precisely what a “Critical issue” should be. Clarit
I've tentatively scheduled discussions for all of August. I've
also specified that the new topic will happen on Tuesday (-1 day),
the "probable decision" will happenon Wednesday (0 day), and the
decision implementation will happen on Thursady (+1 day). These
are all relative to the appropriate we
On Mon, Aug 01, 2011 at 10:22:34PM +, lilyp...@googlecode.com wrote:
> Labels: Type-Defect Priority-Critical Patch-new
heh. About 20 seconds after I uploaded the first release
candidate for 2.16... this is a new record!
Cheers,
- Graham
___
lilypo
Reviewers: ,
Message:
Fixes Issue 1796.
Cheers,
MS
Description:
Prevents lilypond from segfaulting with add-footer = ##f
Please review this at http://codereview.appspot.com/4832046/
Affected files:
M lily/page-breaking.cc
M lily/page-layout-problem.cc
Index: lily/page-breaking.cc
diff -
On 2011/08/01 21:59:06, MikeSol wrote:
From Reinhold's suggestion.
Cheers,
MS
Most recent version passed regtests before the C++ formatting changes.
I've copied and pasted them, so this should pass as well. I'll run a
full set tomorrow.
Cheers,
MS
http://codereview.appspot.com/4837047/
On Aug 1, 2011, at 12:12 PM, Reinhold Kainhofer wrote:
> Am Freitag, 29. Juli 2011, 13:30:30 schrieb m...@apollinemike.com:
>> AUTOMATIC-FOOTNOTES
>>
>> In automatic footnotes, there are three pertinent commands
>> \autoFootnote
>> \autoFootnoteGrob
>> \footnote
>
> For the documentation: The fi
Reviewers: ,
Message:
From Reinhold's suggestion.
Cheers,
MS
Description:
Lets auto numbering of footnotes kick in from commands alone.
Gets rid of footnote-auto-numbering in the paper block.
For now, numbers that are not used are skiped.
Please review this at http://codereview.appspot.com/48
Not a prob, Neil. Pushed as 4ed502a165b3c9a1a65b4632b1e6db91c9655848.
I'll try to get a patch up for the footer problem before I go to bed.
Cheers,
MS
On Aug 1, 2011, at 9:50 PM, n.putt...@gmail.com wrote:
> On 2011/07/31 10:46:54, MikeSol wrote:
>
>> Sorry for having missed them before, Neil
On 2011/07/31 10:46:54, MikeSol wrote:
Sorry for having missed them before, Neil!
Thanks for sorting these.
BTW, you'll probably be interested in this post from lilypond-user-fr:
http://lists.gnu.org/archive/html/lilypond-user-fr/2011-07/msg00127.html
It looks like we need a check to ensure
On Sun, Jul 31, 2011 at 05:17:23PM +0100, Phil Holmes wrote:
> - Original Message - From: "Reinhold Kainhofer"
>
> >To see the warnings, you'll then have to wade through thousands of
> >log files...
>
> make doc already produces hundreds of warnings. It might be
> thousands, I've not cou
I have pushed the grand ficc.py run (including Keith's last fix).
4a401ca1c60f428daa242dbdd102fdb3f327ebfb
For all patch authors for C++ code: please update your local git
tree, and then create a new patch(es), because your current
patch(es) on Rietveld cannot be applied to git master.
If you e
Hello,
)-Original Message-
)From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
)[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of Jean-Charles Malahieude
)Sent: 01 August 2011 18:07
)To: Graham Percival
)Cc: Lily Bugs; lilypond-devel
)Subject: Re: make
Le 01/08/2011 05:11, Graham Percival disait :
On Sun, Jul 31, 2011 at 06:29:33PM +0200, Jean-Charles Malahieude wrote:
No such file: file.itexi
Search path: .:./out-www:.
Extremely normal; happens all the time. :(
Sorry to have disturbed, I had not noticed this manner to label the path.
C
On 31/07/11 23:35, Carl Sorensen wrote:
> On 7/31/11 4:17 PM, "Wols Lists" wrote:
>
>> On 31/07/11 22:00, Janek Warchoł wrote:
>>> 2011/7/31 Wols Lists :
Assuming that it's okay and is applied, I've redone my docu patch.
>>>
>>> Uploaded to Rietveld. I see one trailing whitespace (afte
hi Bertrand,
(I'm not a grand-master, :( )
good that you caught the problem with hole in usable-duration-logs, but,
I think, that makes more comment necessary, see below.
all reviewers: is there a convention about using assertions in C++ code?
http://codereview.appspot.com/4536068/diff/55001/
Am Freitag, 29. Juli 2011, 13:30:30 schrieb m...@apollinemike.com:
> AUTOMATIC-FOOTNOTES
>
> In automatic footnotes, there are three pertinent commands
> \autoFootnote
> \autoFootnoteGrob
> \footnote
For the documentation: The first two are music functions, the third one is a
markup function.
>
Passes Make and reg tests
http://codereview.appspot.com/4800051/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reviewers: Graham Percival,
Message:
Pushed as
Commit 23cdda9506931d5b9a1e75ee8be8be8b74f9084a7c0
James
Description:
Doc: Usage - new option for lilypond-book
Documenting new feature made in
Commit 23cdda9506931d5b9a1e75ee8be8be8b74f9084a7c0
Also for Tracker issue 1730 adding information fo
20 matches
Mail list logo
