LGTM
http://codereview.appspot.com/6330046/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Mon, Jun 25, 2012 at 11:07:38PM +0200, David Kastrup wrote:
The release policies demand 2 weeks without critical regression after a
development release. So far, we have rarely lasted a single week. The
policies are slated for rediscussion at the end of summer. By that
time, we'll not be
On Mon, Jun 25, 2012 at 12:31:45PM +0100, Phil Holmes wrote:
- Original Message - From: Graham Percival
gra...@percival-music.ca
To: Phil Holmes em...@philholmes.net
Cc: Devel lilypond-devel@gnu.org
Sent: Thursday, June 21, 2012 7:47 PM
Subject: Re: LSR updates and translations
Jan Nieuwenhuizen jann...@gnu.org writes:
Graham Percival writes:
201-06-27 GOP2-2 - Stable releases and roadmap (radical change)
http://lilypond.org/~graham/gop/
[empty document]
That's a pretty radical change, already ;-)
Well, it's the chosen policy for a lot of projects in the
On Tue, Jun 26, 2012 at 09:01:20AM +0200, Jan Nieuwenhuizen wrote:
Graham Percival writes:
201-06-27 GOP2-2 - Stable releases and roadmap (radical change)
http://lilypond.org/~graham/gop/
[empty document]
That's a pretty radical change, already ;-)
My parents were visiting for the
David Kastrup d...@gnu.org writes:
Jan Nieuwenhuizen jann...@gnu.org writes:
Graham Percival writes:
201-06-27 GOP2-2 - Stable releases and roadmap (radical change)
http://lilypond.org/~graham/gop/
[empty document]
That's a pretty radical change, already ;-)
Well, it's the chosen
On Tue, Jun 26, 2012 at 07:33:12AM +0200, David Kastrup wrote:
My proposal was just about a release addressing bit rot, namely just
making sure that the equivalent of the existing release 2.14.2 can be
compiled (with no regressions due to the recompilation) on current
systems that insist on
On Mon, Jun 25, 2012 at 11:07:38PM +0200, David Kastrup wrote:
The release blocking issues could be fixed with minor reverts.
The usual release blockers are not revertible. Even if the current set
is get cleared out, history tells us that the time window of two weeks
after unstable release
Graham Percival gra...@percival-music.ca writes:
On Tue, Jun 26, 2012 at 07:33:12AM +0200, David Kastrup wrote:
My proposal was just about a release addressing bit rot, namely just
making sure that the equivalent of the existing release 2.14.2 can be
compiled (with no regressions due to the
On Tue, Jun 26, 2012 at 09:30:12AM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Assuming that this is a 10-minute job, put stuff in the
stable/2.14 git branch, just in case somebody grabs the source
from git tarball.
It's more than 10 minutes since I
Graham Percival gra...@percival-music.ca writes:
On Mon, Jun 25, 2012 at 11:07:38PM +0200, David Kastrup wrote:
The release blocking issues could be fixed with minor reverts.
The usual release blockers are not revertible. Even if the current set
is get cleared out, history tells us that
David Kastrup d...@gnu.org writes:
Graham Percival gra...@percival-music.ca writes:
On Tue, Jun 26, 2012 at 07:33:12AM +0200, David Kastrup wrote:
My proposal was just about a release addressing bit rot, namely just
making sure that the equivalent of the existing release 2.14.2 can be
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: David Kastrup d...@gnu.org
Cc: lilypond-devel@gnu.org
Sent: Tuesday, June 26, 2012 8:34 AM
Subject: Re: Stable release.
On Tue, Jun 26, 2012 at 09:30:12AM +0200, David Kastrup wrote:
Graham Percival
Le mardi 26 juin 2012 à 08:06 +0100, Graham Percival a écrit :
If you're going to rename stuff, I strongly suggest a bigger
rename or you're asking for trouble. I suggest
Documentation/lsr/ ? and Documentation/lsr/new/ ? and then the
corresponding /build/ dirs will be created.
Regarding
Hi David,
On 25.06.2012 18:23, David Nalesnik wrote:
I tried to fix what was amiss in your adaptation of \shape, but I
didn't get very far. This problem seems very complex, and I was only
able to get results by starting from the ground up -- namely, adding
to the function I initially sent.
David Kastrup d...@gnu.org writes:
David Kastrup d...@gnu.org writes:
Graham Percival gra...@percival-music.ca writes:
On Tue, Jun 26, 2012 at 07:33:12AM +0200, David Kastrup wrote:
My proposal was just about a release addressing bit rot, namely just
making sure that the equivalent of the
I'm writing a specification for the updates for the LSR import and come up
against an issue that I don't think we've considered, so I'd like thoughts,
please.
My original assumption would the that the LSR source (which I believe
we've agreed will remain in
Hi,
Just want to say that a thread like this shows clearly:
1. Lilypond is a very advanced and complicated project
2. Several people - even if we always can use more of them - are actively
working on it and care about the quality of the project.
3. Humans make mistakes.
Having said that I
Phil Holmes em...@philholmes.net writes:
I'm writing a specification for the updates for the LSR import and
come up against an issue that I don't think we've considered, so I'd
like thoughts, please.
My original assumption would the that the LSR source (which I
believe we've agreed will
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Tuesday, June 26, 2012 10:02 AM
Subject: Re: Stable release.
David Kastrup d...@gnu.org writes:
David Kastrup d...@gnu.org writes:
Graham Percival gra...@percival-music.ca writes:
On Tue, Jun
Phil Holmes m...@philholmes.net writes:
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Ok, now I am amused. make test of the unmodified 2.14 release branch in
a fresh directory yields
Processing `./01/lily-a2a4d578.ly'
Parsing...
Renaming input to:
Martin Tarenskeen m.tarensk...@zonnet.nl writes:
Hi,
Just want to say that a thread like this shows clearly:
1. Lilypond is a very advanced and complicated project
2. Several people - even if we always can use more of them - are
actively working on it and care about the quality of the
Le mardi 26 juin 2012 à 10:17 +0100, Phil Holmes a écrit :
We have 2 options:
1) Create $LILYPOND_GIT/Documentation/snippets as a straight copy-and-paste,
which is very simple, but proliferates directories in git, and means that an
update should mean deleting all the subdirectories of
Here's my summary of what I think needs to happen with the proposed
management of the snippets:
A tarball of snippets can be downloaded from
http://lsr.dsi.unimi.it/download/. The tarball required is the one tagged
as docs: lsr-snippets-docs--mm-dd.tar.gz. This is unarchived and the
On Tue, Jun 26, 2012 at 11:59:14AM +0200, John Mandereau wrote:
Le mardi 26 juin 2012 à 10:17 +0100, Phil Holmes a écrit :
2) Use a script to update $LILYPOND_GIT/Documentation/snippets. This
deletes all the old snippets except /new; reads all the snippets in the
tarball; adds the
On Tue, Jun 26, 2012 at 01:39:19PM +0100, Phil Holmes wrote:
A
script is run (makesnippets.py?) which iterates over all the
directories in the extracted tarball and all the files in each
directory. It adds a line:
lsrtags = dir-1, dir-2
to each snippet, where dir-n is the directory name
Graham Percival gra...@percival-music.ca writes:
On Tue, Jun 26, 2012 at 01:39:19PM +0100, Phil Holmes wrote:
A
script is run (makesnippets.py?) which iterates over all the
directories in the extracted tarball and all the files in each
directory. It adds a line:
lsrtags = dir-1, dir-2
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: Phil Holmes em...@philholmes.net
Cc: Devel lilypond-devel@gnu.org
Sent: Tuesday, June 26, 2012 2:15 PM
Subject: Re: Importing, updating, translating and building Lilypond snippets
On Tue, Jun 26, 2012 at
On Tue, Jun 26, 2012 at 02:21:43PM +0100, Phil Holmes wrote:
- Original Message - From: Graham Percival
gra...@percival-music.ca
To: Phil Holmes em...@philholmes.net
Cc: Devel lilypond-devel@gnu.org
On Tue, Jun 26, 2012 at 01:39:19PM +0100, Phil Holmes wrote:
lsrtags = dir-1, dir-2
Reviewers: ,
Message:
Please review.
Description:
Add blurb about Kievan notation to changes
Adds a blurb and minimal example to changes.tely indicating support of
Kievan notation.
Please review this at http://codereview.appspot.com/6326056/
Affected files:
M Documentation/changes.tely
*** HTML-formatted version:
lilypond.org/~graham/gop/gop_1.html
*** Summary
We’re not in terrible shape, but we’re not in good shape either.
*** Details
Survey sent:
http://lists.gnu.org/archive/html/lilypond-devel/2012-06/msg00192.html
There were 11 responses:
devA
devB
devC
devD
Graham Percival gra...@percival-music.ca writes:
Mailing list arguments are a trickier issue. It’s clearly a big
problem, but this isn’t something we can fix by waving a change of
policy. I’ll schedule a time to discuss it. We need to do
something about this, although at the moment I have no
On Tue, Jun 26, 2012 at 06:26:34PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Mailing list arguments are a trickier issue. It???s clearly a big
problem, but this isn???t something we can fix by waving a change of
policy. I???ll schedule a time to discuss
On Tue, Jun 26, 2012 at 05:44:19PM +0100, Colin Hall wrote:
On Tue, Jun 26, 2012 at 06:26:34PM +0200, David Kastrup wrote:
Decent communication in electronic media
is one of the things I am spectacularly bad at. One thing that has
turned out to be effective at times is meeting people in
Graham Percival gra...@percival-music.ca writes:
On Tue, Jun 26, 2012 at 05:44:19PM +0100, Colin Hall wrote:
On Tue, Jun 26, 2012 at 06:26:34PM +0200, David Kastrup wrote:
Decent communication in electronic media
is one of the things I am spectacularly bad at. One thing that has
turned
Colin Hall wrote Tuesday, June 26, 2012 5:44 PM
On Tue, Jun 26, 2012 at 06:26:34PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Mailing list arguments are a trickier issue. It???s clearly a big
problem, but this isn???t something we can fix by waving a
David Kastrup d...@gnu.org writes:
Graham Percival gra...@percival-music.ca writes:
On Tue, Jun 26, 2012 at 05:44:19PM +0100, Colin Hall wrote:
On Tue, Jun 26, 2012 at 06:26:34PM +0200, David Kastrup wrote:
Decent communication in electronic media
is one of the things I am spectacularly
On 26 juin 2012, at 18:26, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Mailing list arguments are a trickier issue. It’s clearly a big
problem, but this isn’t something we can fix by waving a change of
policy. I’ll schedule a time to discuss it. We need to do
Trevor Daniels t.dani...@treda.co.uk writes:
Colin Hall wrote Tuesday, June 26, 2012 5:44 PM
On Tue, Jun 26, 2012 at 06:26:34PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Mailing list arguments are a trickier issue. It???s clearly a big
problem, but
Le 26/06/2012 09:24, Graham Percival disait :
Well, we had at least a week when the only release-critical bug
was the po-replace translation thing. It's a bit silly that we
couldn't have a release due to a 5-line texinfo documentation
thing, and in retrospect I should have done a hostile revert
Jean-Charles Malahieude lily...@orange.fr writes:
Le 26/06/2012 09:24, Graham Percival disait :
Well, we had at least a week when the only release-critical bug
was the po-replace translation thing. It's a bit silly that we
couldn't have a release due to a 5-line texinfo documentation
thing,
On Tue, Jun 26, 2012 at 07:19:28PM +0200, Jean-Charles Malahieude wrote:
Le 26/06/2012 09:24, Graham Percival disait :
Well, we had at least a week when the only release-critical bug
was the po-replace translation thing. It's a bit silly that we
couldn't have a release due to a 5-line texinfo
I seem to remember that Werner was away until the middle of August,
and the school holidays last until August 21st.
I've now booked a fly to Dortmund (in addition to visiting my two
children there will be probably a performance of my piece for Cello
orchestra), staying there from Aug 15th to
[...] I'm afraid I can't be present. I'm not really a core
developer, so couldn't contribute much to the discussion anyway.
This doesn't matter. It's fully sufficient that you are capable of
drinking beer, I presume :-)
Werner
___
Hi Jan-Peter,
First of all, I agree with David Kastrup that this is a situation where a
deep fix is in order so that simultaneous ties may be tweaked directly.
Your example is working as expected :)
Glad to hear it!
To make it (more) usable, I think, we need wrapper functions, to avoid
Am 23.06.2012 11:11, schrieb Marc Hohl:
Am 23.06.2012 11:06, schrieb Benkő Pál:
hi Marc,
http://codereview.appspot.com/6305115/diff/1/scm/bar-line.scm
File scm/bar-line.scm (right):
http://codereview.appspot.com/6305115/diff/1/scm/bar-line.scm#newcode83
scm/bar-line.scm:83: (define
On Tue, Jun 26, 2012 at 06:26:34PM +0200, David Kastrup wrote:
So the core data would be Dortmund Germany (about 10 miles from there)
and the proposal for a date would Friday August 17th to Tuesday August
21st, or one week later.
Any idea about the connectivity with nearby airports? Flying to
Not quite up to the ideal standard of GOP proposals, but there's a
lot of interest and this should be enough to see what way the wind
is blowing.
html-formatted version:
http://lilypond.org/~graham/gop/gop_3.html
*** Summary
Let’s drop the “any unintended change” thing, and go totally with
the
LGTM
I made these changes in lilypond-book.py in the 2.15.40 binary
(different line numbers, but lines the same) and I can confirm they fix
the problem on Windows.
Thanks Julien!
Trevor
http://codereview.appspot.com/6342048/
___
lilypond-devel
Graham Percival gra...@percival-music.ca writes:
On Tue, Jun 26, 2012 at 06:26:34PM +0200, David Kastrup wrote:
So the core data would be Dortmund Germany (about 10 miles from there)
and the proposal for a date would Friday August 17th to Tuesday August
21st, or one week later.
Any idea
On Tue, Jun 26, 2012 at 1:26 PM, David Kastrup d...@gnu.org wrote:
Mailing list arguments are a trickier issue. It’s clearly a big
problem, but this isn’t something we can fix by waving a change of
policy. I’ll schedule a time to discuss it. We need to do
something about this, although at the
For 20:00 MDT Thursday, June 28
Critical:
Issue 2623
http://code.google.com/p/lilypond/issues/detail?id=2623: Lilypond-book
fails due to include_path.insert call in lilypond-book.py - R 6342048
http://codereview.appspot.com/6342048/
Documentation:
Issue 2625
Graham Percival graham at percival-music.ca writes:
Let’s drop the “any unintended change” thing, and go totally with
the regression tests. Tests pass? We can make a stable release.
I don't know. Maybe that would be alright. I'm not sure.
The 'Regression' label would be come more important,
53 matches
Mail list logo
