Il giorno mar 10 nov 2015 alle 5:11, John Gourlay
ha scritto:
Federico,
Thank you very much for your help.
I ran "sudo usermod -aG vboxsf $(whoami)" and it fixed the
permission-denied problem. Making this happen by default in LilyDev
sounds like a good idea to me.
Great, I'll do it. Thanks
Il giorno ven 6 nov 2015 alle 20:49, John Gourlay
ha scritto:
Federico,
I do have another small LilyDev/VirtualBox problem. I’m having
trouble using the Shared Folders feature to give me access to a
folder in my Mac file system from LilyDev in VirtualBox. The folder I
want to share is /Users
Federico,
I do have another small LilyDev/VirtualBox problem. I’m having trouble using
the Shared Folders feature to give me access to a folder in my Mac file system
from LilyDev in VirtualBox. The folder I want to share is
/Users/John/Documents/LilyPond in the Mac file system. It’s privilege i
Il giorno lun 2 nov 2015 alle 17:18, John Gourlay
ha scritto:
The PAE setting was the problem. Thanks for helping, and I apologize
for overlooking that step in the instructions.
Ok, good. And welcome to LilyPond!
Let me know if you find any problem in LilyDev.
The image you are using does not
of LilyPond hoping to get involved in development. I’ve
>> installed VirtualBox and with it I’ve created a virtual machine with the
>> LilyDev disk image. The Debian installation completed, but it won’t run;
>> VirtualBox gives me a popup error message saying, “A critical erro
gives me a popup error
message saying, “A critical error has occurred while running the
virtual machine…” Do you have any suggestions for overcoming this
problem?
I’m running Mac OS X version 10.10.5, VirtualBox version 5.0.8, and
the LilyDev disk image lilydev-4.0-i386.hybrid.iso. What other
I’m a new user of LilyPond hoping to get involved in development. I’ve
installed VirtualBox and with it I’ve created a virtual machine with the
LilyDev disk image. The Debian installation completed, but it won’t run;
VirtualBox gives me a popup error message saying, “A critical error has
David Kastrup wrote Friday, September 27, 2013 1:33 PM
> I think after letting 2.17.27 settle for a few days, we are ready to
> create the branch. We still might make another 2.17 release afterwards
> to get some exposure to final fixes (like the \fill-line markup), but it
> better not have any
- Original Message -
From: "David Kastrup"
To: "Federico Bruni"
Cc: "lilypond-devel"
Sent: Friday, September 27, 2013 1:33 PM
Subject: Re: no critical: 2.18 is close?
Federico Bruni writes:
I see there's no critical issue in the tracker.
Federico Bruni writes:
> I see there's no critical issue in the tracker.
> I remember that you used to publish release candidates of next stable when
> we have no critical issues.
> So I wonder if the releae of 2.18 is close or there's something that it's
> blockin
I see there's no critical issue in the tracker.
I remember that you used to publish release candidates of next stable when
we have no critical issues.
So I wonder if the releae of 2.18 is close or there's something that it's
blocking it..
Just curious.. and also I want to organize
"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?
>>
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?
>> I
> 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
>
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
David,
Have you noticed http://code.google.com/p/lilypond/issues/detail?id=2935 a
critical regression?
--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
en reverted so far is
> 512d405d07aba8742658902b105a94ebbd40c2dc "Get texidoc translations out
> of snippets source files", it's a non-Critical Maintainability/Build
> issue, so it shouldn't prevent a release. IWBN to have it for
> translators before 2.16, but it certai
Il giorno lun, 02/07/2012 alle 12.50 +0100, Phil Holmes ha scritto:
> It appears to kill the build system on a non-multi CPU make. See Mike's
> emails concerning screech-and-boink. I can replicate the problem with make,
> but if I run make -jX (X from 3 to 9) the build succeeds. Looks like
>
- Original Message -
From: "John Mandereau"
To: "Graham Percival"
Cc:
Sent: Monday, July 02, 2012 12:21 PM
Subject: Re: building master / fixed all Critical?
Il giorno dom, 01/07/2012 alle 23.29 +0100, Graham Percival ha scritto:
I'm not certain where we
0c2dc "Get texidoc translations out
of snippets source files", it's a non-Critical Maintainability/Build
issue, so it shouldn't prevent a release. IWBN to have it for
translators before 2.16, but it certainly must go under more testing.
Sorry,
John
__
Graham Percival writes:
> I'm not certain where we stand. Over the weekend, some patches
> were pushed (by accident?) to master. One (or more?) of those
> commits broke compiling, and were reverted. This fix was (or will
> be?) pushed to staging, and people can (or can not?) now compile
> git
On 2 juil. 2012, at 01:26, Keith OHara wrote:
> Graham Percival percival-music.ca> writes:
>
>> Could we get a clear note about which commit(s) were reverted and
>> are presumably in limbo? If the remaining commits fixed 2604 and
>> 2524 (which at a first glance appear to be resolved), then co
On Sun, Jul 1, 2012 at 6:29 PM, Graham Percival
wrote:
> I'm not certain where we stand. Over the weekend, some patches
> were pushed (by accident?) to master. One (or more?) of those
> commits broke compiling, and were reverted. This fix was (or will
I was just able to make doc from scratch w
Graham Percival percival-music.ca> writes:
> Could we get a clear note about which commit(s) were reverted and
> are presumably in limbo? If the remaining commits fixed 2604 and
> 2524 (which at a first glance appear to be resolved), then could
> we get those marked as fixed so that I can try ma
I'm not certain where we stand. Over the weekend, some patches
were pushed (by accident?) to master. One (or more?) of those
commits broke compiling, and were reverted. This fix was (or will
be?) pushed to staging, and people can (or can not?) now compile
git master without problems.
Could we g
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
p;cells=tiles
> (recent build and maintainability issues - important for improving
> development workflow)
>
As I guess, the most critical bugs are those flagged as: Critical, so this
list<http://code.google.com/p/lilypond/issues/list?can=2&q=Type%3DCritical&colspec=ID+Type+Sta
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
get Finale and Sibelius. They are not a problem we need to address
> since they are competing in a different space.
I don't fully agree, but i guess discusssing this is not that important.
>> That means not only fixing critical bugs, but also: anticipating
>> future stability pr
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}
>>>
ompeting in a different space. Our real problem is
LilyPond.
> Probably some of you will return to the old row - is a goal of a
> Lilypond to substitue Finale or compete with Sibellius. I think there
> is no point in loosing your energy *and time* on that. Instead we
> should do as
s. Probably some of you will return to the old row - is a
goal of a Lilypond to substitue Finale or compete with Sibellius. I think
there is no point in loosing your energy *and time* on that.
Instead we should do as much as possible to constantly improve Lilypond.
That means not only fixing critical bu
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
Lilypond will improve in a slow pace, letting Finale and Sibellius gain more
>> and more users.
So what?
it's not a competition.
>> Probably some of you will return to the old row - is a goal
>> of a Lilypond to substitue Finale or compete with Sibellius. I think t
substitue Finale or compete with Sibellius. I think there
> is no point in loosing your energy and time on that.
> Instead we should do as much as possible to constantly improve Lilypond.
> That means not only fixing critical bugs, but also: anticipating future
> stability problems, constantl
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
riticals, so let's make a
stable release before an obstruction occurs!"). To do so, we would
have to work more as a team, less independently. How can we achieve
that if GOP7 showed that we don't want to?
By the way, you mentioned earlier that there are issues much more
severe and
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
at we reached during that GOP discussion, and I am not
> interested in re-opening that discussion.
>
> Bottom line: I will not be calling anything a "stable release", or
> even a "release candidate", if there are issues which are known to
> fall under the c
leasable material and platform-specific development. I see very
> little correlation between what I'd call a measure of stability, and
> what the current set of "Critical bugs" entails.
While this sounds reasonable, i'm not sure if a policy could be
written that would ref
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
pening development. _That's_ what we should be cutting
the stable branch from. And _then_ try getting it ported timely to the
platforms that have, lamentably, a rather lacklustre progress of
releasable material and platform-specific development. I see very
little correlation between what I'd
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.
>
ring that GOP discussion, and I am not
interested in re-opening that discussion.
Bottom line: I will not be calling anything a "stable release", or
even a "release candidate", if there are issues which are known to
fall under the current definition of a "Critical issue&qu
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)
f nobody is going to protest in the next few hours) is
>> to revert the flawed fix.
>
> I think that's entirely reasonable. IMO, if there's no clear
> offer of a fix within 48 hours of a bad commit, we should revert
> it.
>
>> The other critical bug appears to b
gt; to revert the flawed fix.
I think that's entirely reasonable. IMO, if there's no clear
offer of a fix within 48 hours of a bad commit, we should revert
it.
> The other critical bug appears to be related with multithreading, and I
> consider it likely, given its random ap
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 fix
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
1 - 100 of 217 matches
Mail list logo
