Hans Aberg haber...@telia.com writes:
On 26 Sep 2013, at 17:16, Phil Holmes m...@philholmes.net wrote:
The section originates with me but I got diverted into trying to
create a more elegant solution for how to rewrite accidentals in
transposed music. It was all related to the need for an
Graham Percival writes:
On Thu, Sep 26, 2013 at 02:05:44PM +0200, Jan Nieuwenhuizen wrote:
- plain email-based patch submission using a benevolent dictator,
ie, use git the way it was designed and is still used by the
creators (linux, git).
Are you volunteering to be that benevolent
On 27 Sep 2013, at 00:05, Janek Warchoł janek.lilyp...@gmail.com wrote:
Hi,
2013/9/26 Hans Aberg haber...@telia.com:
On 26 Sep 2013, at 17:16, Phil Holmes m...@philholmes.net wrote:
Joseph Wakeling wrote:
I was also rather discouraged by the fact that the quarter-tone arrow
notation
On 27 Sep 2013, at 08:45, David Kastrup d...@gnu.org wrote:
Hans Aberg haber...@telia.com writes:
On 26 Sep 2013, at 17:16, Phil Holmes m...@philholmes.net wrote:
The section originates with me but I got diverted into trying to
create a more elegant solution for how to rewrite accidentals
On 26/09/13 18:38, David Kastrup wrote:
You commented on the issue where this patch originated as late as July:
URL:http://code.google.com/p/lilypond/issues/detail?id=1278#c7. So
it's hard to argue that it was not discoverable to you.
This July I got an email update from the issue, and
Joseph Rushton Wakeling joseph.wakel...@webdrake.net writes:
On 26/09/13 18:38, David Kastrup wrote:
You commented on the issue where this patch originated as late as July:
URL:http://code.google.com/p/lilypond/issues/detail?id=1278#c7. So
it's hard to argue that it was not discoverable to
Hello,
*Countdown – October 1st – 06:00 GMT* *
* *
* *
* *
* *
* *
* *
* *
* *
*
3582http://code.google.com/p/lilypond/issues/detail?id=3582q=label%3APatch-countdownsort=patchcolspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified
Enhancement
David Kastrup countdown Patch:
On 27/09/13 03:44, Graham Percival wrote:
On Thu, Sep 26, 2013 at 03:12:27PM +0200, Joseph Rushton Wakeling wrote:
This risks becoming another corrosive discussion,
Then WTF are you starting it?
Because I had hoped that what I said was sufficiently qualified not to create
bad feeling.
LGTM. You might want to add to your comment at the top: Also convert
the file to Unix line endings.
https://codereview.appspot.com/13720049/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
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 my translation
Federico Bruni fedel...@gmail.com 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
blocking it..
The
- Original Message -
From: David Kastrup d...@gnu.org
To: Federico Bruni fedel...@gmail.com
Cc: lilypond-devel lilypond-devel@gnu.org
Sent: Friday, September 27, 2013 1:33 PM
Subject: Re: no critical: 2.18 is close?
Federico Bruni fedel...@gmail.com writes:
I see there's no critical
Reviewers: Julien Rioux, dak,
Message:
Initial patch to check the principle is OK. Will require documentation
updates before it's pushed. Please review Eluze's Python.
Description:
Add backup option to convert-ly (Issue 3572)
Please review this at https://codereview.appspot.com/14040043/
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
Comment #6 on issue 3566 by d...@gnu.org: Grace notes should be autobeamed
I don't think the current state warrants a convert-ly rule: it does not
seem like the previous behavior is used to any reasonable degree, and it
can always be reverted by removing the engraver. Anything that has
Hello,
Would it be worthwhile that we add an extra sentence in the 'release news'
(Documentation / web / news-front.itexi) informing users that they might
need to use convert.ly - just that we occasionally get users 'forgetting'
or not knowing that they _might_ need to use convert.ly for newer
I did mean to consider doing something like that with the most recent release,
but also forgot...
Please remember that new releases can require syntax changes. Please use
convert-ly (web link) to make most of these automatically.
--
Phil Holmes
- Original Message -
From: James
This suggestion from David sounded like a good default:
Make numbered backups for files that have numbered backups already.
https://codereview.appspot.com/14040043/diff/1/scripts/convert-ly.py
File scripts/convert-ly.py (right):
I've added a snippet (http://lsr.dsi.unimi.it/LSR/Item?id=751) to master
that explains how to set stem direction based on surrounding notes. Anyone
object to my adding it to selected snippets in
http://www.lilypond.org/doc/v2.16/Documentation/notation/inside-the-staff#stems -
I think it makes
Phil Holmes wrote Friday, September 27, 2013 8:54 PM
I've added a snippet (http://lsr.dsi.unimi.it/LSR/Item?id=751) to master
that explains how to set stem direction based on surrounding notes. Anyone
object to my adding it to selected snippets in
LGTM
Question:
considering LSR-update, I recently added an earlier version of it to the
LSR
http://lsr.dsi.unimi.it/LSR/Item?id=887
Should I replace it with this one?
https://codereview.appspot.com/13826047/
___
lilypond-devel mailing list
21 matches
Mail list logo
