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 what the
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 tweaked
a
Graham Percival graham at percival-music.ca writes:
** Rationale
Bug squad members are confused, users are confused, and (to a
certain extent) Graham just makes up the rules for “Critical” as
he goes along. Let’s get some clarity here.
Giving priority to issues which hinder development
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: lilypond-devel@gnu.org
Cc: Phil Holmes em...@philholmes.net
Sent: Tuesday, August 02, 2011 6:22 AM
Subject: GOP-PROP 8: issue priorities
I'm expecting a moderate amount of discussion for this one.
We have had several single-commit branches recently. Those appear in
the history just as merge with master and require additional work for
tracking the changes, worse so when the branchoff point is a long way
backwards.
So please make it a habit to do
git rebase origin
before doing
git
Graham Percival gra...@percival-music.ca writes:
Priority-medium:
* highest level for graphical output problems
* highest level for undocumentated new features
Actually, I read this first as bugs in undocumented features can't have
high priority, carrying the message if you don't
Hello,
)-Original Message-
)From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
)[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of Phil Holmes
)Sent: 02 August 2011 09:29
)To: Graham Percival; lilypond-devel@gnu.org
)Subject: Re: GOP-PROP 8: issue
- Original Message -
From: James Lowe james.l...@datacore.com
To: Phil Holmes m...@philholmes.net; Graham Percival
gra...@percival-music.ca; lilypond-devel@gnu.org
[snip]
) Priority-postponed:
)
)* No fix expected for at least two years.
)
)I don't actually see the point of this,
Pushed by Graham as 2d30bf30c3af6e7c4f1d158ec095c67450adea79
http://codereview.appspot.com/4808051/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
2011/7/31 Janek Warchoł lemniskata.bernoull...@gmail.com:
Wow, i'm CCed! Why?
You are on my list as aesthetic guru (+ good engraving practices).
And also because Gmail's Consider including feature suggested me to
Cc you (and finally because it usually makes the person reply to the
message,
As many will know, I've been looking at the make process, and in particular
make doc. I've found that there is a very quick way to remake docs into a
PDF when any of the source text has changed. For notation, this takes about
2 minutes on my machine, compared with 2 hours 20 minutes for a
- Original Message -
From: Xavier Scheuer x.sche...@gmail.com
Since it seems I'm not the only one to consider that Full measure rest
should take more horizontal space (as much horizontal space as a note
of the same duration), could someone open a new issue for this on the
tracker?
Reviewers: Graham Percival,
Message:
Please review.
Description:
This regtest had a number of old lines of syntax and produces warnings
with the latest version of LilyPond. It also uses tabs for indents.
This is a cleaner, warning-free version.
Please review this at
On Tue, Aug 02, 2011 at 05:01:00PM +0100, Phil Holmes wrote:
As many will know, I've been looking at the make process, and in
particular make doc. I've found that there is a very quick way to
remake docs into a PDF when any of the source text has changed. For
notation, this takes about 2
On Tue, Aug 02, 2011 at 10:32:15AM +0200, David Kastrup wrote:
We have had several single-commit branches recently. Those appear in
the history just as merge with master and require additional work for
tracking the changes, worse so when the branchoff point is a long way
backwards.
So
Graham Percival gra...@percival-music.ca writes:
On Tue, Aug 02, 2011 at 10:32:15AM +0200, David Kastrup wrote:
We have had several single-commit branches recently. Those appear in
the history just as merge with master and require additional work for
tracking the changes, worse so when the
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: Phil Holmes m...@philholmes.net
Cc: lilypond-devel@gnu.org
Sent: Tuesday, August 02, 2011 6:31 PM
Subject: Re: Quick way to recreate docs
On Tue, Aug 02, 2011 at 05:01:00PM +0100, Phil Holmes wrote:
As many will
Le 02/08/2011 20:48, Phil Holmes disait :
- Original Message - From: Graham Percival
To: Phil Holmes
Sent: Tuesday, August 02, 2011 6:31 PM
Subject: Re: Quick way to recreate docs
On Tue, Aug 02, 2011 at 05:01:00PM +0100, Phil Holmes wrote:
As many will know, I've been looking at the
On Tue, Aug 02, 2011 at 08:46:28PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
http://lilypond.org/doc/v2.15/Documentation/contributor/minor-release-checklist
If I need to have a few git rebase origin in those commands,
could you please push a fix to
On Tue, Aug 02, 2011 at 07:48:14PM +0100, Phil Holmes wrote:
- Original Message - From: Graham Percival
gra...@percival-music.ca
On Tue, Aug 02, 2011 at 05:01:00PM +0100, Phil Holmes wrote:
Off the top of my head, I suspect that this can be done with
make out=www
On Tue, Aug 02, 2011 at 07:48:12AM +, Keith OHara wrote:
I'm curious first what we want the priority field to mean.
Ding ding, I think we have a winner. That sentence is the crux of
the whole thing.
Probably we do not mean literally the priority with which contributors will
give
LGTM, although I initially misread the commit message as saying that the
*new* version uses tabs for indents. Maybe change that to the old
version used tabs, just for extra clarity ?
http://codereview.appspot.com/4811066/
___
lilypond-devel mailing
http://codereview.appspot.com/4811066/diff/1/input/regression/mozart-hrn-3.ly
File input/regression/mozart-hrn-3.ly (right):
http://codereview.appspot.com/4811066/diff/1/input/regression/mozart-hrn-3.ly#newcode25
input/regression/mozart-hrn-3.ly:25: \fill-line { This music is part of
the
W dniu 1 sierpnia 2011 16:47 użytkownik Wols Lists
antli...@youngman.org.uk napisał:
On 31/07/11 23:35, Carl Sorensen wrote:
Do we need four bars? Why not just do three bars -- one with capoPitch '(),
another with capoPitch set, and a third with capoVertical?
We like to get examples and
2011/8/2 Xavier Scheuer x.sche...@gmail.com:
2011/7/31 Janek Warchoł lemniskata.bernoull...@gmail.com:
Wow, i'm CCed! Why?
You are on my list as aesthetic guru (+ good engraving practices).
OMG! That's an honour, thanks!
And also because Gmail's Consider including feature suggested me to
http://codereview.appspot.com/4800051/diff/12002/Documentation/notation/chords.itely
File Documentation/notation/chords.itely (right):
http://codereview.appspot.com/4800051/diff/12002/Documentation/notation/chords.itely#newcode516
Documentation/notation/chords.itely:516: In make-pitch, leave
Passes make and reg tests
http://codereview.appspot.com/4832046/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
2011/7/31 Phil Holmes m...@philholmes.net:
Don't think this is a problem, but it is a bit interesting. I've been
trying to run my pixel comparator to compare 15.7 to 15.5 and getting a
difference in the bar lines of every image - presumably owing to the work to
stop the PDF artefacts.
On 02/08/11 21:24, n.putt...@gmail.com wrote:
http://codereview.appspot.com/4800051/diff/12002/Documentation/notation/chords.itely
File Documentation/notation/chords.itely (right):
http://codereview.appspot.com/4800051/diff/12002/Documentation/notation/chords.itely#newcode516
Hi David,
sorry but i don't understand if this applies to me? (i don't have push ability)
2011/8/2 David Kastrup d...@gnu.org:
Graham Percival gra...@percival-music.ca writes:
On Tue, Aug 02, 2011 at 10:32:15AM +0200, David Kastrup wrote:
We have had several single-commit branches recently.
Keith,
sorry for the delayed answer, i had to sort out my repository because
of grand-fixccing, and didn't know how to open eps files that are
created by regtests (eventually i compiled a few suspicious regtests
by hand).
In general, your patch is wonderful! It does the things i hoped for for
http://codereview.appspot.com/4832046/diff/2001/lily/page-layout-problem.cc
File lily/page-layout-problem.cc (right):
http://codereview.appspot.com/4832046/diff/2001/lily/page-layout-problem.cc#newcode282
lily/page-layout-problem.cc:282: warning (Must have a footer to add
footnotes.);
(_ (must
Am Tuesday, 2. August 2011, 23:14:46 schrieb Jan Warchoł:
Regardless of whether this applies to me or not, does using git pull
-r instead of plain git pull make this problem irrelevant, or am i
wrong?
I think so.
'git pull --rebase' is basically the same as 'git fetch; git rebase
Reviewers: ,
Message:
Patch ready for review.
But also see
http://code.google.com/p/lilypond/issues/detail?id=1776#c6
as there are still some points I am not clear on on this function that
may need more doc additions.
Description:
Doc: Added \compoundMeter function to NR
Tracker 1776.
Reviewers: ,
Message:
This patch is the one with which I found the problem in the build
system. While its introduction of a +nan.0 somewhere in the works does
not bode well for it, all of the snippets in input/regression compile
cleanly before the build system crashes (see issue 1799), and I
Hello, makes ok but during eg check I get:
--snip--
reading input/regression/out-test/tablature-tie-spanner-1.signature
Traceback (most recent call last):
File
/home/jlowe/lilypond-git/build/scripts/build/out/output-distance, line
1261, in module
main ()
File
Yo,
Anybody interested in writing / modifying a scheme script to
indent scheme files? This is a much easier problem than C++ code.
I've found standalone scripts for PLT Racket and common lisp:
http://evalwhen.com/scmindent/index.html
I think that they need some minor tweaking to make them run
On 3 August 2011 01:27, mts...@gmail.com wrote:
Reviewers: ,
Message:
This patch is the one with which I found the problem in the build
system. While its introduction of a +nan.0 somewhere in the works does
not bode well for it, all of the snippets in input/regression compile
cleanly
38 matches
Mail list logo
