Hi all,
We've been passing proposals faster than we can implement them.
That's particularly a shame because there's a *huge* amount of
friction and unpleasantness that can be avoided by spending a few
hours on implementing a number of those proposals.
We will continue with the existing proposals,
Pushed as b4ff85a2416e4b80deb9eef8329cd230ee4dc944 and preceding.
http://codereview.appspot.com/5023044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Fri, Sep 23, 2011 at 09:43:01PM -0400, Colin Campbell wrote:
> Instead, we present a special, one time only, batch as
> requested by Mike Solomon.
Am I correct that these have not been checked by James? I don't
think we should call this a "countdown". By all means suggest
that people review
Reviewers: ,
Message:
commit f84eab93e732ed2b9aa50436202a28f34243c6
closing issue
Description:
Doc: NR Clarify finer point of repeat unfold
This is for tracker issue 1801.
Explain as an example, that \repeat unfold 2 {music expression} is
not always the same as writing out the music expressi
FOR 21:00 MDT 20110925
As it happens, the one time I both travel (to my Mother's place across the
continent) *and* arrange to borrow a browser to cover my patch meister
schedule, there are no patches in the issue tracker ready to go. Instead, we
present a special, one time only, batch as requ
On Fri, Sep 23, 2011 at 11:40:19PM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> > dev/staging
>
> There you are.
Thanks, b4ff85a2416e4b80deb9eef8329cd230ee4dc944 built all the
docs on git master, so I've merged it with master.
Cheers,
- Graham
LGTM
http://codereview.appspot.com/5075047/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am Friday, 23. September 2011, 23:00:45 schrieb Dave Plater:
> If lilypond is unable to use guile 2.0 it's the only
> hope although my personal opinion is the easiest route is fixing the
> compilation problem. A failed documentation build I can work around by
> using the doc tarball a failed progra
Graham Percival writes:
> On Fri, Sep 23, 2011 at 03:03:46PM +0200, David Kastrup wrote:
>> But we still need to find a solution where I have a chance of getting
>> work done.
>
> dev/staging
>
> I just realized that I forgot to add this to the proposal. I'll
> do that later tonight and send an
Regtests and docs are there. The last upload, however, seems to have
influences from a few unrelated commits. Rietveld is too complicated
for me.
On the plus side, a working version (compiles the docs as far as I can
tell) has been pushed to dev/staging.
http://codereview.appspot.com/5023044/
Graham Percival writes:
> On Fri, Sep 23, 2011 at 03:03:46PM +0200, David Kastrup wrote:
>> But we still need to find a solution where I have a chance of getting
>> work done.
>
> dev/staging
There you are.
--
David Kastrup
___
lilypond-devel maili
David Kastrup wrote Friday, September 23, 2011 10:17 AM
Subject: Re: GOP-PROP 12: keep master in ready-to-release state
(probabledecision)
"Trevor Daniels" writes:
My preference is for a single staging branch. Major patches
would be
pushed there rather than to master after a successful R
On 09/23/2011 05:37 PM, Ian Hulin wrote:
Hi Dave,
Lilypond (V2.14) needs to have Guile V1.8.7 minimum and V1.8.8 maximum
to work. We are currently working on migrating to use Guile V2.0 but
it's slow progress owing to the close-knit integration between Lily
and Guile. The migration work will n
make doc problem solved on my system. I can confirm that make and make
doc run successfully with this patch.
http://codereview.appspot.com/4951062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-d
Graham Percival writes:
> On Fri, Sep 23, 2011 at 03:03:46PM +0200, David Kastrup wrote:
>> But we still need to find a solution where I have a chance of getting
>> work done.
>
> dev/staging
>
> I just realized that I forgot to add this to the proposal. I'll
> do that later tonight and send an
On Fri, Sep 23, 2011 at 03:03:46PM +0200, David Kastrup wrote:
> But we still need to find a solution where I have a chance of getting
> work done.
dev/staging
I just realized that I forgot to add this to the proposal. I'll
do that later tonight and send an updated version.
Or better yet -- dev
On Fri, Sep 23, 2011 at 05:03:21PM +0100, Phil Holmes wrote:
> You know, I'm wondering if this serves any purpose. It's a
> humungous thing that takes an age to load and display, and for a
> long time has had a load of missing images, bad links, etc. No-one
> complained much and no-one really see
On Fri, 23 Sep 2011 00:07:39 -0700, m...@apollinemike.com
wrote:
On Sep 23, 2011, at 8:56 AM, Keith OHara wrote:
On Thu, 22 Sep 2011 23:11:08 -0700, m...@apollinemike.com
wrote:
On Sep 23, 2011, at 6:38 AM, Keith OHara wrote:
Phil Holmes philholmes.net> writes:
There are 2 significa
You know, I'm wondering if this serves any purpose. It's a humungous thing
that takes an age to load and display, and for a long time has had a load of
missing images, bad links, etc. No-one complained much and no-one really
seemed to notice. Yet we lose the images on web-examples and get a u
Out of curiosity: guile2 will make rendering faster for lilypond?
Other advantages?
Since compilation time of big scores annoys lots of people, that would
be good to have.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mail
Hi Dave,
Lilypond (V2.14) needs to have Guile V1.8.7 minimum and V1.8.8 maximum
to work. We are currently working on migrating to use Guile V2.0 but
it's slow progress owing to the close-knit integration between Lily
and Guile. The migration work will not be available in time for
V2.16, either.
Hi Reinhold and Janek,
I hope I got it right this time. I didn't include the bit about
. This will be part of a seperate patch.
BTW: I noticed that the midi-block is not always inserted in every .ly
file (this is not related to my patch). I will do some testing...
Thanks for your help!
patrick
David Kastrup writes:
> Reinhold Kainhofer writes:
>
>> Am Friday, 23. September 2011, 11:17:32 schrieb David Kastrup:
>>
>>> It is a compromise between the damage and the good developers manage
>>> to do. The higher the number of developers, the more important it
>>> becomes to avoid damage, s
On 09/23/2011 02:15 PM, Peekay Ex wrote:
Dave,
On Fri, Sep 23, 2011 at 12:54 PM, Dave Plater wrote:
On 09/23/2011 01:40 PM, Dave Plater wrote:
I am the sole maintainer and packager of openSUSE lilypond and I have a
build failure in factory builds that appears to be guile related,
unfortunate
On 09/23/2011 02:03 PM, David Kastrup wrote:
Dave Plater writes:
On 09/23/2011 01:40 PM, Dave Plater wrote:
I am the sole maintainer and packager of openSUSE lilypond and I
have a build failure in factory builds that appears to be guile
related,
unfortunately guile is new to me and I'm battli
Dave,
On Fri, Sep 23, 2011 at 12:54 PM, Dave Plater wrote:
> On 09/23/2011 01:40 PM, Dave Plater wrote:
>>
>> I am the sole maintainer and packager of openSUSE lilypond and I have a
>> build failure in factory builds that appears to be guile related,
>> unfortunately guile is new to me and I'm ba
Dave Plater writes:
> On 09/23/2011 01:40 PM, Dave Plater wrote:
>> I am the sole maintainer and packager of openSUSE lilypond and I
>> have a build failure in factory builds that appears to be guile
>> related,
>> unfortunately guile is new to me and I'm battling to get all the
>> packages used
Hm, I didn't understand all of this. What do I have to change in
musicxml2ly? My
idea was to use the "description" misc field for a custom header
variable named
'miscellaneous' by default. I was thinking about implementing a cmd
line option
('-t' and '--texinfo') to be able to use the 'texin
I am the sole maintainer and packager of openSUSE lilypond and I have a build failure in factory builds that appears to be guile related,
unfortunately guile is new to me and I'm battling to get all the packages used by lilypond synced up and built for 11.4 in
home:plater:lilypond. I've also had
On 2011/09/22 13:26:54, Reinhold wrote:
Welcome to the wonderful world of LilyPond development!
:)
Most changes look fine, but there are some things that can't be
submitted yet.
See my comments.
Most important: Please edit the source file in scripts/musicxml2ly.py
and don't
modify the in
Reinhold Kainhofer writes:
> Am Friday, 23. September 2011, 11:17:32 schrieb David Kastrup:
>
>> It is a compromise between the damage and the good developers manage
>> to do. The higher the number of developers, the more important it
>> becomes to avoid damage, since damage blocks everybody, an
"m...@apollinemike.com" writes:
> When I say "the problem is limited to a specific case," I mean that I
> am not sure if these two bugs (fingerings being gobbled up and the
> StrokeFinger issue) are related, not that my patch seeks to address a
> specific symptom of a bug without eliminating the
Am Friday, 23. September 2011, 11:17:32 schrieb David Kastrup:
> "Trevor Daniels" writes:
> > How would this code be reviewed? Do you envisage still
> > uploading to Reitfeld? Would this be before pushing to
> > dev/* or after? I still think this is a complication too far.
> > Certainly it need
On Sep 23, 2011, at 11:26 AM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> On Sep 23, 2011, at 10:16 AM, Keith OHara wrote:
>>
>>> On Fri, 23 Sep 2011 01:03:33 -0700, m...@apollinemike.com
>>> wrote:
>>>
Slur::outside_callback has changed, however (see
dd855b6da
Hello,
On Fri, Sep 23, 2011 at 8:59 AM, Graham Percival
wrote:
> On Fri, Sep 23, 2011 at 09:55:26AM +0200, David Kastrup wrote:
>> I am somewhat surprised that the patch passed testing by someone else,
>> though. It would seem that doc builds are not part of that.
>
> I think that James only doe
"m...@apollinemike.com" writes:
> On Sep 23, 2011, at 10:16 AM, Keith OHara wrote:
>
>> On Fri, 23 Sep 2011 01:03:33 -0700, m...@apollinemike.com
>> wrote:
>>
>>>
>>> Slur::outside_callback has changed, however (see
>>> dd855b6da30a050359a94ac719e0fc37a2fca666).
>>>
>>> Perhaps this fixes the
"Trevor Daniels" writes:
> Graham Percival
>
>> Developers doing medium-large fixes: examples include beam
>> collisions, music function rewriting, Flag grobs, etc. All this
>> work should go on separate branches (e.g. dev/flag-grob,
>> dev/scheme-music-functions). Once the code is merged, the br
On Sep 23, 2011, at 10:16 AM, Keith OHara wrote:
> On Fri, 23 Sep 2011 01:03:33 -0700, m...@apollinemike.com
> wrote:
>
>>
>> Slur::outside_callback has changed, however (see
>> dd855b6da30a050359a94ac719e0fc37a2fca666).
>>
>> Perhaps this fixes the problem?
>>
>
> Maybe. You'll have to a
Reinhold Kainhofer writes:
> On Fr., 23. Sep. 2011 09:55:26 CEST, David Kastrup wrote:
>> I am somewhat surprised that the patch passed testing by someone else,
>> though. It would seem that doc builds are not part of that.
>
> Nope, because it's the regtetsts' task, so only the regtests are
>
Graham Percival
Developers doing medium-large fixes: examples include beam
collisions, music function rewriting, Flag grobs, etc. All this
work should go on separate branches (e.g. dev/flag-grob,
dev/scheme-music-functions). Once the code is merged, the branch
should be removed. People can stil
On Fr., 23. Sep. 2011 09:55:26 CEST, David Kastrup wrote:
> I am somewhat surprised that the patch passed testing by someone else,
> though. It would seem that doc builds are not part of that.
Nope, because it's the regtetsts' task, so only the regtests are checked. It's
also a practical issue
On Fri, 23 Sep 2011 01:03:33 -0700, m...@apollinemike.com
wrote:
Slur::outside_callback has changed, however (see
dd855b6da30a050359a94ac719e0fc37a2fca666).
Perhaps this fixes the problem?
Maybe. You'll have to ask the author of dd855b if that might have affected
problems
associated wi
David Kastrup writes:
> Here is the problem: \with-link declares its argument type wrong
> (declares symbol? and uses #"label", a string). My patch has the
> side-effect that markup commands actually check their argument lists for
> correctness. Previously it just let any Scheme argument throug
On Sep 23, 2011, at 10:00 AM, Keith OHara wrote:
> On Fri, 23 Sep 2011 00:07:39 -0700, m...@apollinemike.com
> wrote:
>
>>> \relative f {
>>> \voiceOne
>>> e''8( e
>>> e c)-1-2
>>> }
>>
>> Also compiles fine on current master...weird...
>>
>
>
> The problem is associated with the mess
sorry, I forgot to send this on Wednesday.
http://lilypond.org/~graham/gop/gop_12.html
** Proposal summary
Let’s keep git master in ready-to-release state all the time. In
particular, assume that git master could become the next major
stable release at any time. If that makes you pause and wonde
Proposal accepted now. I'll start implementing it soon.
http://lilypond.org/~graham/gop/gop_11.html
** Proposal summary
Our source code hosting is confused: some branches of lilypond
savannah are confusing and should removed, while other parts of
our source code aren’t in a repository at all!
On Fri, 23 Sep 2011 00:07:39 -0700, m...@apollinemike.com
wrote:
\relative f {
\voiceOne
e''8( e
e c)-1-2
}
Also compiles fine on current master...weird...
The problem is associated with the message "no solution found for Bezier
intersection"
in bezier.cc, which seems it would
On Fri, Sep 23, 2011 at 09:55:26AM +0200, David Kastrup wrote:
> I am somewhat surprised that the patch passed testing by someone else,
> though. It would seem that doc builds are not part of that.
I think that James only does a normal make and make check; that's
doable in 3 minutes on his comput
David Kastrup writes:
> Peekay Ex writes:
>
>> Hello again..
>>
>> On Fri, Sep 23, 2011 at 5:34 AM, Peekay Ex wrote:
>>> Hello,
>>>
>>> On Fri, Sep 23, 2011 at 3:46 AM, Reinhold Kainhofer
>>> wrote:
Am Friday, 23. September 2011, 04:35:06 schrieben Sie:
> > fatal error: failed files:
Peekay Ex writes:
> Hello again..
>
> On Fri, Sep 23, 2011 at 5:34 AM, Peekay Ex wrote:
>> Hello,
>>
>> On Fri, Sep 23, 2011 at 3:46 AM, Reinhold Kainhofer
>> wrote:
>>> Am Friday, 23. September 2011, 04:35:06 schrieben Sie:
> fatal error: failed files: "be/lily-48175def.ly"
A de
On Fri, Sep 23, 2011 at 09:07:39AM +0200, m...@apollinemike.com wrote:
> On Sep 23, 2011, at 8:56 AM, Keith OHara wrote:
>
> > \relative f {
> >\voiceOne
> >e''8( e
> >e c)-1-2
> > }
>
> Also compiles fine on current master...weird...
FWIW, I can confirm this. With
13d24779fd6b71e81
On Sep 23, 2011, at 8:56 AM, Keith OHara wrote:On Thu, 22 Sep 2011 23:11:08 -0700, m...@apollinemike.com wrote:On Sep 23, 2011, at 6:38 AM, Keith OHara wrote:Phil Holmes philholmes.net> writes:There are 2 significant problems I've found with 2.15.12. The first isshown in t
On Sep 23, 2011, at 8:41 AM, Keith OHara wrote:
> mike apollinemike.com apollinemike.com> writes:
>
>> On Sep 23, 2011, at 6:38 AM, Keith OHara wrote:
>>
>>> Phil Holmes philholmes.net> writes:
There are 2 significant problems I've found with 2.15.12. The first is
shown in t
53 matches
Mail list logo