"m...@mikesolomon.org" writes:
> There are two critical issues that we're going to have to start
> seriously thinking about now if 2.18 is going to happen anytime soon:
>
> https://code.google.com/p/lilypond/issues/detail?id=2733
>
> I'm not comfortable ma
On Wed, Mar 27, 2013 at 6:54 AM, Werner LEMBERG wrote:
>
>> https://code.google.com/p/lilypond/issues/detail?id=2656
>>
>> This is really bad. I agree that it is critical. I unfortunately
>> have no way to test this, but do people have an ETA for fixing this?
>> If not, it will hold 2.18 up for
On 27 mars 2013, at 07:54, Werner LEMBERG wrote:
>
>> https://code.google.com/p/lilypond/issues/detail?id=2656
>>
>> This is really bad. I agree that it is critical. I unfortunately
>> have no way to test this, but do people have an ETA for fixing this?
>> If not, it will hold 2.18 up for a
> https://code.google.com/p/lilypond/issues/detail?id=2656
>
> This is really bad. I agree that it is critical. I unfortunately
> have no way to test this, but do people have an ETA for fixing this?
> If not, it will hold 2.18 up for a long time, in which it may be
> worth pushing the translate
There are two critical issues that we're going to have to start seriously
thinking about now if 2.18 is going to happen anytime soon:
https://code.google.com/p/lilypond/issues/detail?id=2733
I'm not comfortable marking this critical: not because it is not critical for
Laura, nor beca
On Fri, Apr 6, 2012 at 6:11 PM, Graham Percival
wrote:
> On Fri, Apr 06, 2012 at 06:04:39PM +0200, m...@apollinemike.com wrote:
>> Release candidate anyone? Or have we already had a version bump? I can
>> build it, Graham, if you're over hours.
>
> It's already building.
Sorry, guys, bad news:
On Fri, Apr 06, 2012 at 06:04:39PM +0200, m...@apollinemike.com wrote:
> Release candidate anyone? Or have we already had a version bump? I can
> build it, Graham, if you're over hours.
It's already building. I've been trying to build it for the past
few days, but I can only do it after bootin
Release candidate anyone? Or have we already had a version bump? I can build
it, Graham, if you're over hours.
Cheers,
MS
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Thanks for all answers.
On 8 January 2012 23:47, Janek Warchoł wrote:
> W dniu 8 stycznia 2012 10:11 użytkownik James napisał:
> > Start by looking here:
> >
> http://code.google.com/p/lilypond/issues/list?can=2&q=&sort=priority&colspec=ID&x=type&y=priority&mode=grid&cells=tiles
>
> Umm, guys,
Janek Warchoł writes:
> According to our motto the aim of LilyPond is "music engraving to
> everyone" - i'd say it's a very good goal. It would mean that a
> person with average computer skills (like navigating a web browser and
> using word processor) should be able to create very good engravin
W dniu 8 stycznia 2012 02:54 użytkownik Graham Percival
napisał:
> On Sun, Jan 08, 2012 at 01:52:41AM +0100, Łukasz Czerwiński wrote:
>> * Let's assume that I would like to help in developing Lilypond, but
>>I don't have my own idea, what part of it I could improve. What
>>wou
On Jan 8, 2012, at 2:54 AM, Graham Percival wrote:
> On Sun, Jan 08, 2012 at 01:52:41AM +0100, Łukasz Czerwiński wrote:
>>
>> Are there some guidelines how to write new code to work in the same
>> manner as the already written code?
>
> We have a contributor's guide. It is not complete, but t
Hello,
2012/1/8 Łukasz Czerwiński :
> What's the aim of Lilypond?
err..
"LilyPond is a music engraving program, devoted to producing the
highest-quality sheet music possible. It brings the aesthetics of
traditionally engraved music to computer printouts."
> And why isn't it competing with Fina
On Sun, Jan 08, 2012 at 01:52:41AM +0100, Łukasz Czerwiński wrote:
>As for all the emails that were written it the last two days, I believe
>that a sort of coordination is needed in each project.
We have the amount of coordination that we have chosen.
> * Let's assume that I would li
First of all I would like to apologize for misjudging Lilypond project.
As for all the emails that were written it the last two days, I believe
that a sort of coordination is needed in each project. Maybe for some of
them there must be one boss with many programmers and designers, while for
other
David,
2012/1/7 David Kastrup :
> I really don't quite get the point of complaining that I provide
> alternative ways of accessing functionality. Nobody forces you to make
> use of them.
2012/1/7 David Kastrup :
> In the light of the focus of the work I have been doing for several
> months, I ha
Janek Warchoł writes:
> What i want to say is, i'm afraid you might have forgotten how it
> feels to be a non-programmer. It's not a joke that for average person
> that wants to produce some notation, it's hard enough to use text
> input.
In the light of the focus of the work I have been doing
Janek Warchoł writes:
> 2012/1/5 David Kastrup :
>>
>> Janek Warchoł writes:
>>
>>> 2012/1/4 David Kastrup :
\layout {
\layout-from { \compressFullBarRests
\override Score.SpacingSpanner #'common-shortest-duration =
#(ly:make-moment 6 10)
}
etc...
2012/1/5 David Kastrup :
>
> Janek Warchoł writes:
>
>> 2012/1/4 David Kastrup :
>>> \layout {
>>> \layout-from { \compressFullBarRests
>>> \override Score.SpacingSpanner #'common-shortest-duration =
>>> #(ly:make-moment 6 10)
>>> }
>>> etc...
>>> }
>>
>> ok... However - i'm very so
"m...@apollinemike.com" writes:
> On Jan 5, 2012, at 9:14 AM, David Kastrup wrote:
>
>> "m...@apollinemike.com" writes:
>>
>>> On Jan 5, 2012, at 1:20 AM, Janek Warchoł wrote:
>>>
Correct me if i'm wrong, but my impression is that
there is no particular direction in which we are goin
On Jan 5, 2012, at 9:14 AM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> On Jan 5, 2012, at 1:20 AM, Janek Warchoł wrote:
>>
>>> Correct me if i'm wrong, but my impression is that
>>> there is no particular direction in which we are going.
>>
>> I'm sure that other people have t
"m...@apollinemike.com" writes:
> On Jan 5, 2012, at 1:20 AM, Janek Warchoł wrote:
>
>> Correct me if i'm wrong, but my impression is that
>> there is no particular direction in which we are going.
>
> I'm sure that other people have their pet projects as well. The
> ensemble of these projects i
On Jan 5, 2012, at 1:20 AM, Janek Warchoł wrote:
> Correct me if i'm wrong, but my impression is that
> there is no particular direction in which we are going.
>
I think that it is very difficult to set these goals because different things
interest different people. I know that Bertrand and I
Janek Warchoł writes:
> 2012/1/4 David Kastrup :
\settingsFrom is actually returning a Scheme expression for \with to
use. It makes things rather simpler than more complex, even though it
constitutes a Scheme expression.
>>>
>>> Um... i would really love to be able to type
>>> \l
Adding Luke to recipients again... (please remember to include him as
he's not signed to our mailing lists),
2012/1/4 David Kastrup :
> Łukasz Czerwiński writes:
>> Regarding all those fragments of Janek's and David's emails: For some time
>> I have been observing how bug are being fixed in Lily
2012/1/4 David Kastrup :
>>> \settingsFrom is actually returning a Scheme expression for \with to
>>> use. It makes things rather simpler than more complex, even though it
>>> constitutes a Scheme expression.
>>
>> Um... i would really love to be able to type
>> \layout {
>> \compressFullBar
2012/1/4 James :
> hello,
>
> On 3 Jan 2012, at 22:26, Janek Warchoł wrote:
>> I might have given you a wrong impression, i don't think its really
>> that bad. There is some teamwork, but no leader indeed.
>
> to use an English expression ... poppycock!
>
> Janek you may have not noticed that the
David Kastrup writes:
> Janek Warchoł writes:
>
>>> \layout {
>>> \context {
>>> \Score
>>> \with \settingsFrom { \compressFullBarRests }
>>> }
>>> \context {
>>> \Staff
>>> \with \settingsFrom { \accidentalStyle modern }
>>> }
>>> }
>>> }
>>> \end{lilypond}
>>>
Łukasz Czerwiński writes:
> On 3 January 2012 21:47, Janek Warchoł wrote:
>
>>
>> > I am a TeX specialist, system programmer, Emacs specialist, the GNU
>> > maintainer (and a rather pitiful one) for AUCTeX (lytex and itexi
>> > anybody? preview-latex for Lilypond?)
>
> Mmm... Preview for Lilypon
On 3 January 2012 21:47, Janek Warchoł wrote:
>
> > I am a TeX specialist, system programmer, Emacs specialist, the GNU
> > maintainer (and a rather pitiful one) for AUCTeX (lytex and itexi
> > anybody? preview-latex for Lilypond?)
Mmm... Preview for Lilypond? Sounds like a good start for a real
Janek Warchoł writes:
>> \layout {
>> \context {
>> \Score
>> \with \settingsFrom { \compressFullBarRests }
>> }
>> \context {
>> \Staff
>> \with \settingsFrom { \accidentalStyle modern }
>> }
>> }
>> }
>> \end{lilypond}
>>
>> \ph is a music function written in S
hello,
On 3 Jan 2012, at 22:26, Janek Warchoł wrote:
> Hi Luke,
>
> nice to see you joining the discussion :)
>
> W dniu 3 stycznia 2012 23:06 użytkownik Łukasz Czerwiński
> napisał:
>>> That's like + from me!
>>> In general, i agree that we should think in a more 'release-oriented'
>>> w
Hi Luke,
nice to see you joining the discussion :)
W dniu 3 stycznia 2012 23:06 użytkownik Łukasz Czerwiński
napisał:
>> That's like + from me!
>> In general, i agree that we should think in a more 'release-oriented'
>> way ("last stable release was half a year ago, so we should make
>> anot
2012/1/3 David Kastrup :
> Janek Warchoł writes:
>
>> 2012/1/3 David Kastrup :
>
>>> LilyPond needs to get into a state where, say, half the
>>> engravers are written and maintained in Scheme. And by "Scheme" I don't
>>> mean "Scheme at the level Nicolas can barely handle" but "Scheme a
>>> Fortr
Janek Warchoł writes:
> 2012/1/3 David Kastrup :
>> LilyPond needs to get into a state where, say, half the
>> engravers are written and maintained in Scheme. And by "Scheme" I don't
>> mean "Scheme at the level Nicolas can barely handle" but "Scheme a
>> Fortran programmer would not have all t
vs
>> > stable?
>
> Yeah, especially since Carl was *already* making good progress on
> the GUB-related critical issues.
>
>> http://xkcd.com/386/>
>
> yep.
>
> Let's cut to the chase: I am an evil semi-overlord. I jealously
> guard my ssh login t
elease dev after dev release vs
>> > stable?
>
> Yeah, especially since Carl was *already* making good progress on
> the GUB-related critical issues.
>
>> http://xkcd.com/386/>
>
> yep.
>
> Let's cut to the chase: I am an evil semi-overlord. I jeal
nce Carl was *already* making good progress on
the GUB-related critical issues.
> http://xkcd.com/386/>
yep.
Let's cut to the chase: I am an evil semi-overlord. I jealously
guard my ssh login to lilypond.org (along with Han-Wen's and
Jan's), I am fickle, and I like to play with
2012/1/3 David Kastrup :
> Janek Warchoł writes:
>
>> 2012/1/3 David Kastrup :
>>> The Learning Guide and the Notation Guide need a complete rereading and
>>> reorganization, and it is not like the Extending Guide is in
>>> significantly better shape.
>>
>> I'd like to fix them too, but i don't ha
Janek Warchoł writes:
> 2012/1/3 David Kastrup :
>> The Learning Guide and the Notation Guide need a complete rereading and
>> reorganization, and it is not like the Extending Guide is in
>> significantly better shape.
>
> I'd like to fix them too, but i don't have time for everything i want
> :(
2012/1/3 Graham Percival :
> It so happens that none of these Critical issues are really
> fixable by reverting a single commit.
>
> [...]
ok, thanks for this explanation!
>> Is finding them an easy (no knowledge
>> needed, a complete set of dumbed-down instructions ca
James writes:
> Hello,
>
> On 3 January 2012 12:53, Han-Wen Nienhuys wrote:
>> On Tue, Jan 3, 2012 at 10:36 AM, Werner LEMBERG wrote:
If we refuse thinking about stable releases by taking GUB as an
excuse, the grand next stable release that will benefit users of
many operating sy
Han-Wen Nienhuys writes:
> On Tue, Jan 3, 2012 at 10:36 AM, Werner LEMBERG wrote:
>>> If we refuse thinking about stable releases by taking GUB as an
>>> excuse, the grand next stable release that will benefit users of
>>> many operating systems is likely to fall in the class "too little,
>>> to
"m...@apollinemike.com" writes:
> One in-the-middle approach is to check out package managers that are
> offering LilyPond releases. I know, for example, that brew offers a
> version of LilyPond on Mac OS X. If we provide a list of package
> managers and how-tos for the techno-phobic, that may
Hello,
On 3 January 2012 12:53, Han-Wen Nienhuys wrote:
> On Tue, Jan 3, 2012 at 10:36 AM, Werner LEMBERG wrote:
>>> If we refuse thinking about stable releases by taking GUB as an
>>> excuse, the grand next stable release that will benefit users of
>>> many operating systems is likely to fall i
Werner LEMBERG writes:
>> If we refuse thinking about stable releases by taking GUB as an
>> excuse, the grand next stable release that will benefit users of
>> many operating systems is likely to fall in the class "too little,
>> too late".
>
> I second David. Given that we develop within a GNU
On Tue, Jan 3, 2012 at 10:36 AM, Werner LEMBERG wrote:
>> If we refuse thinking about stable releases by taking GUB as an
>> excuse, the grand next stable release that will benefit users of
>> many operating systems is likely to fall in the class "too little,
>> too late".
>
> I second David. Giv
On Jan 3, 2012, at 1:36 PM, Werner LEMBERG wrote:
>
>> If we refuse thinking about stable releases by taking GUB as an
>> excuse, the grand next stable release that will benefit users of
>> many operating systems is likely to fall in the class "too little,
>> too late".
>
> I second David. Give
> If we refuse thinking about stable releases by taking GUB as an
> excuse, the grand next stable release that will benefit users of
> many operating systems is likely to fall in the class "too little,
> too late".
I second David. Given that we develop within a GNU environment, bugs
specific to
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
No. I have an Ubuntu VM which I use for quick experiments and a very
fast Ubuntu PC which I use for full builds. But I support lilypond
because I _use_ it for typesetting music on a _Windows_ machine. Take
away that abilit
"Phil Holmes" writes:
> From: "David Kastrup"
> To:
> Sent: Tuesday, January 03, 2012 11:44 AM
> Subject: Re: critical issues
>
>> "Phil Holmes" writes:
>>
>>> From: "David Kastrup"
>>> To:
>&
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, January 03, 2012 11:44 AM
Subject: Re: critical issues
"Phil Holmes" writes:
From: "David Kastrup"
To:
There is a _reason_ the remaining OSX and Windows based developers
a
"Phil Holmes" writes:
> From: "David Kastrup"
> To:
>
>> There is a _reason_ the remaining OSX and Windows based developers
>> are doing (definitely important) documentation and web site work.
>> They are to a large degree locked out and dependent on support from
>> surplus GNU/Linux-based deve
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, January 03, 2012 7:55 AM
Subject: Re: critical issues
Graham Percival writes:
On Tue, Jan 03, 2012 at 01:03:08AM +0100, David Kastrup wrote:
Graham Percival writes:
> We could certainly consider droppin
Graham Percival writes:
> On Tue, Jan 03, 2012 at 01:03:08AM +0100, David Kastrup wrote:
>> Graham Percival writes:
>>
>> > We could certainly consider dropping support for OSX or windows.
>>
>> That sort of token solidarity is actually counterproductive:
>> if you believe that non-releases le
ion about which commits caused our currently open
> critical regression, does it mean that's impossible to tell or simply
> noone tried to find them?
It so happens that none of these Critical issues are really
fixable by reverting a single commit.
- lilypond-book came from a general rew
(sorry for double-post)
2012/1/2 Graham Percival :
> On Mon, Jan 02, 2012 at 10:23:28PM +0100, David Kastrup wrote:
>> Graham Percival writes:
>> > If you are aware of any other issues which fall under the
>> > definition (i.e. a reproducible failure to build lilypond from
>> > scratch,
>>
>> On
lect your intentions; they're a bit too vague.
And even with current guidelines its always possible to say "i think
that we shouldn't make a stable release despite having 0 critical
issues, because current master is shabby and we have some major
changes going in the codebase&quo
On Tue, Jan 03, 2012 at 01:03:08AM +0100, David Kastrup wrote:
> Graham Percival writes:
>
> > We could certainly consider dropping support for OSX or windows.
>
> That sort of token solidarity is actually counterproductive:
> if you believe that non-releases lead to non-users,
yes
> and you t
Graham Percival writes:
> On Mon, Jan 02, 2012 at 10:23:28PM +0100, David Kastrup wrote:
>> Graham Percival writes:
>>
>> > This was the result of between 25 to 40 emails in August 2011 on
>> > lilypond-devel. A quick scan didn't reveal your name amongst
>> > those emails, but we simply cannot
her all examples and
separate the whole "accidental problem" into separate, yet meaningful,
issues).
If you think that i really should attack these critical issues at all
costs, let me know and i'll consider it.
> We could certainly consider dropping support for OSX or windows.
>
On Mon, Jan 02, 2012 at 10:23:28PM +0100, David Kastrup wrote:
> Graham Percival writes:
>
> > This was the result of between 25 to 40 emails in August 2011 on
> > lilypond-devel. A quick scan didn't reveal your name amongst
> > those emails, but we simply cannot afford to revisit every policy
>
Graham Percival writes:
> On Mon, Jan 02, 2012 at 09:59:47PM +0100, David Kastrup wrote:
>>
>> I see the following critical issues:
> -snip-
>>
>> There is, actually, a wagonload of other changes underfoot that does not
>> appear quite compatible with relea
On Mon, Jan 02, 2012 at 09:59:47PM +0100, David Kastrup wrote:
>
> I see the following critical issues:
-snip-
>
> There is, actually, a wagonload of other changes underfoot that does not
> appear quite compatible with releasing a version called "stable" to me.
> It
I see the following critical issues:
2160document LILYPOND_WEB_MEDIA_GIT
2100Patch: CG: explanation of branches for the impatient
1948Windows install clobbered system PATH
1943lilypond after 2.15.8 fails on x86 Macs
1933Lilypond-book requires msvcrt again
1933, 1943, 1948
Wols Lists writes:
> On 31/07/11 17:47, David Kastrup wrote:
>> Windows 2000 (not NT-based IIRC) does not usefully employ memory
>> protection IIRC, so likely Cygwin does not add all too much on top.
>
> Windows 2000 most definitely IS NT-based. You're thinking of Windows ME,
> which is the last
On 31/07/11 17:47, David Kastrup wrote:
> Windows 2000 (not NT-based IIRC) does not usefully employ memory
> protection IIRC, so likely Cygwin does not add all too much on top.
Windows 2000 most definitely IS NT-based. You're thinking of Windows ME,
which is the last of the DOS7/Win9x line.
Cheer
Graham Percival writes:
> On Sun, Jul 31, 2011 at 10:26:11AM +0200, David Kastrup wrote:
>> Modern operating systems don't give your code any leftovers from a
>> previous run. That would be a security violation.
>
> I'm certain that I've seen an uninitialized variable being
> 123456789 in some c
On Sun, Jul 31, 2011 at 10:26:11AM +0200, David Kastrup wrote:
> Modern operating systems don't give your code any leftovers from a
> previous run. That would be a security violation.
I'm certain that I've seen an uninitialized variable being
123456789 in some cases, and 0 in others. I sincerly
Am Sunday, 31. July 2011, 07:45:20 schrieb Graham Percival:
> I haven't seen any interest in
> http://code.google.com/p/lilypond/issues/detail?id=1732
> This is unfortunate, since it means that we can't have a release
> candidate on Aug 01.
Without a reproducible test case, it's simply not possi
2011/7/31 David Kastrup :
> Graham Percival writes:
>
>> On Sun, Jul 31, 2011 at 09:42:36AM +0200, David Kastrup wrote:
>>> Graham Percival writes:
>>>
>>> > I haven't seen any interest in
>>> > http://code.google.com/p/lilypond/issues/detail?id=1771
>>>
>>> My take on this (if nobody is going
Graham Percival writes:
> On Sun, Jul 31, 2011 at 10:04:59AM +0200, David Kastrup wrote:
>> But this bug has been reported as occuring non-deterministically even in
>> successive runs on the same machine, and there are rather few things
>> that can introduce such stochastic behavior (another poss
On Sun, Jul 31, 2011 at 10:04:59AM +0200, David Kastrup wrote:
> But this bug has been reported as occuring non-deterministically even in
> successive runs on the same machine, and there are rather few things
> that can introduce such stochastic behavior (another possibility would
> be timer-trigge
David Kastrup wrote Sunday, July 31, 2011 8:42 AM
Graham Percival writes:
I haven't seen any interest in
http://code.google.com/p/lilypond/issues/detail?id=1771
My take on this (if nobody is going to protest in the next few
hours) is
to revert the flawed fix.
+1
The original bug fi
Graham Percival writes:
> On Sun, Jul 31, 2011 at 09:42:36AM +0200, David Kastrup wrote:
>> Graham Percival writes:
>>
>> > I haven't seen any interest in
>> > http://code.google.com/p/lilypond/issues/detail?id=1771
>>
>> My take on this (if nobody is going to protest in the next few hours)
Graham Percival writes:
> On Sun, Jul 31, 2011 at 09:42:36AM +0200, David Kastrup wrote:
>> Graham Percival writes:
>>
>> > I haven't seen any interest in
>> > http://code.google.com/p/lilypond/issues/detail?id=1771
>>
>> My take on this (if nobody is going to protest in the next few hours)
On Sun, Jul 31, 2011 at 09:42:36AM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> > I haven't seen any interest in
> > http://code.google.com/p/lilypond/issues/detail?id=1771
>
> My take on this (if nobody is going to protest in the next few hours) is
> to revert the flawed fix.
I
Graham Percival writes:
> I haven't seen any interest in
> http://code.google.com/p/lilypond/issues/detail?id=1771
My take on this (if nobody is going to protest in the next few hours) is
to revert the flawed fix.
Reason: we get rid of a critical issue.
The original bug fixer does not appear
eople have said that they would like to have stable releases
more regularly. Some people have expressed a willingness to work
on a team, i.e. spending a few hours a week on stuff that
(potentially) doesn't interest them in the least, simply to keep
momentum.
I implore those people to investigate
Hey guys,
I've been busy/distracted/sick for the past week, and I'll
continue to be busy/distracted/sick for the next ten days. I'm
also fed up with announcing a release candidate and then
discovering that there's a known critical issue that wasn't on the
tracker a day later.
1) if you're worki
On Sun, Jan 23, 2011 at 10:29:11AM -0500, Boris Shingarov wrote:
> The Lilypond project has a very specific set of objectives. There
> is a defined set of procedures, a roadmap, a set of criteria of
> what is acceptable to go into the codebase, etc.
This is true of any (well-organized) project.
e rules, and how big is
the problem?
Well on one hand, none of today's Critical Issues in Lilypond,
are on the list of priorities for our project. So even if we had
20 full-time developers, it wouldn't help with releasing the next
stable version.
On the other hand, we have implemente
Pushed to Rietveld:http://codereview.appspot.com/4056043
Note that there is a trailing whitespace error on line 47 of the diff.
Cheers,
MS
On Jan 20, 2011, at 5:13 AM, Keith OHara wrote:
> On Thu, 20 Jan 2011 01:33:10 -0800, Keith OHara wrote:
>
>> ... because that fixes 1120 more
>> solidly
On Thu, 20 Jan 2011 01:33:10 -0800, Keith OHara wrote:
... because that fixes 1120 more
solidly and removes the cause for issues 1474 and 1472,
Well, reverting ee0488 removes the cause of our /noticing/ issue 1472
(multi-measure rests colliding with key signatures).
The way that KeySigs res
%{ Fellow Contributors,
The patches look like they do the job, and give clean regression tests,
but the developers are hesitant. I am not a programmer, and I cannot
read minds, but I can tell you what makes *me* hesitant.
Look at issue 1120. A lyric syllable covering more than one note spread
th
On 1/19/11 6:06 PM, "Mike Solomon" wrote:
> Also works, also passes make check, also attached, also on Rietveld:
> http://codereview.appspot.com/4006044
> From Neil's e-mail, it seems that he advocates this solution because "Clefs
> are taken into account (shown by the yellow-blue skyline pair) w
On 1/19/11 6:06 PM, "Mike Solomon" wrote:
> Also works, also passes make check, also attached, also on Rietveld:
> http://codereview.appspot.com/4006044
> From Neil's e-mail, it seems that he advocates this solution because "Clefs
> are taken into account (shown by the yellow-blue skyline pair
Also works, also passes make check, also attached, also on Rietveld:
http://codereview.appspot.com/4006044
From Neil's e-mail, it seems that he advocates this solution because "Clefs are
taken into account (shown by the yellow-blue skyline pair) when calculating
horizontal skylines for NonMusica
On 1/19/11 4:33 PM, "Mike Solomon" wrote:
> Got it.
>
> Then, here is the state of things:
>
> 1/6
> Bug is first reported on the bug list.
>
> 1/7
> Neil reports adding a default 'extra-spacing-height to key signature.
>
> 1/10
> Keith confirms that this works and that he gets a clean make
Got it.
Then, here is the state of things:
1/6
Bug is first reported on the bug list.
1/7
Neil reports adding a default 'extra-spacing-height to key signature.
1/10
Keith confirms that this works and that he gets a clean make check.
1/13
Phil holmes reports the regression on the bugtracker (2.
On 1/19/11 2:51 PM, "m...@apollinemike.com" wrote:
> Graham et all,
>
> I have read all of the postings and am up to date - I meant "what next" as a
> general question to the community in the sense of "would anyone who was
> actually involved in the pushing of this commit (Joe - I see your name
On 1/19/11 2:51 PM, "m...@apollinemike.com" wrote:
> Graham et all,
>
> I have read all of the postings and am up to date - I meant "what next" as a
> general question to the community in the sense of "would anyone who was
> actually involved in the pushing of this commit (Joe - I see your name
Graham et all,
I have read all of the postings and am up to date - I meant "what next" as a
general question to the community in the sense of "would anyone who was
actually involved in the pushing of this commit (Joe - I see your name
associated with it - how much work did you do on it?) like t
On Wed, Jan 19, 2011 at 04:31:47PM -0500, m...@apollinemike.com wrote:
> result of git bisect for issue 1472
>
> ee0488f3aa19e0060b6e17c46a4d88cb9d57c489 is the first bad commit
> Fix 1120.
>
> What next?
Umm. Next you read the emails on lilypond-devel which have been
discussing this fo
result of git bisect for issue 1472
ee0488f3aa19e0060b6e17c46a4d88cb9d57c489 is the first bad commit
commit ee0488f3aa19e0060b6e17c46a4d88cb9d57c489
Author: Joe Neeman
Date: Fri Jun 18 16:53:17 2010 +0300
Fix 1120.
Don't add vertical padding to the skylines that are used for
h
2011/1/19 Graham Percival :
> On Wed, Jan 19, 2011 at 04:32:21PM +0100, Francisco Vila wrote:
>> 2011/1/19 Graham Percival :
>> >it's no problem for me to recompile lilypond
>> > 30 or 40 times.
>>
>> Finding a commit out of 40 by git-bisect shouldn't need to recompile
>> more than log2(40)=5.32 ,
My bad!
I'll take on 1472...gulp...
Cheers,
Mike
On Jan 19, 2011, at 7:29 AM, Graham Percival wrote:
> On Wed, Jan 19, 2011 at 06:57:27AM -0500, m...@apollinemike.com wrote:
>> I'll take care of 1472, but I need a copy of Valentin's opera.
>
> Valentin's opera is available as a git checkout:
>
On Wed, Jan 19, 2011 at 04:32:21PM +0100, Francisco Vila wrote:
> 2011/1/19 Graham Percival :
> >it's no problem for me to recompile lilypond
> > 30 or 40 times.
>
> Finding a commit out of 40 by git-bisect shouldn't need to recompile
> more than log2(40)=5.32 , this gives 6 times in the worst ca
2011/1/19 Graham Percival :
>it's no problem for me to recompile lilypond
> 30 or 40 times.
Finding a commit out of 40 by git-bisect shouldn't need to recompile
more than log2(40)=5.32 , this gives 6 times in the worst case.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.co
2011/1/19 Graham Percival :
> On 1/19/11, Benkő Pál wrote:
>>> I tried briefly looking at the opera a few days ago, but it didn't
>>> compile in 2.12.3 or 2.13.46, so I gave up after a few minutes.
>>> Finding a minimal example that works in both 2.12.3 and 2.13.46
>>> might be tricky,
>>
>> tonig
1 - 100 of 159 matches
Mail list logo
