Re: Doc: NR Clarify repeats w\ partials and barchecks (issue 61530043)

2014-02-16 Thread tdanielsmusic
A few suggestions for extra clarity ... https://codereview.appspot.com/61530043/diff/20001/Documentation/notation/repeats.itely File Documentation/notation/repeats.itely (right): https://codereview.appspot.com/61530043/diff/20001/Documentation/notation/repeats.itely#newcode168

Re: Doc: Point-and-Click has wrong default value and ref to SVGoutput needs adding (issue 61630045)

2014-02-16 Thread Trevor Daniels
pkx1...@gmail.com wrote Sunday, February 16, 2014 6:51 AM Looking at the TexInfo page for @acronym https://www.gnu.org/software/texinfo/manual/texinfo/html_node/_0040acronym.html It doesn't seem to give us anything that useful and perhaps (as it also says in the link above): - In

Emergency call. Or not.

2014-02-16 Thread David Kastrup
I find that I'm currently dead-locking in decision-making with a somewhat tedieous task. Here is what it boils down to: basically git checkout -b translation origin/translation git log --reverse --no-merges origin/translation..origin Documentation Now in a separate window check every commit on

Re: Emergency call. Or not.

2014-02-16 Thread James
David On 16 Feb 2014, at 14:45, David Kastrup d...@gnu.org wrote: I find that I'm currently dead-locking in decision-making with a somewhat tedieous task. Here is what it boils down to: basically git checkout -b translation origin/translation git log --reverse --no-merges

Re: Emergency call. Or not.

2014-02-16 Thread Phil Holmes
- Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Sunday, February 16, 2014 2:45 PM Subject: Emergency call. Or not. I find that I'm currently dead-locking in decision-making with a somewhat tedieous task. Here is what it boils down to: basically

Re: Emergency call. Or not.

2014-02-16 Thread David Kastrup
Phil Holmes m...@philholmes.net writes: Let's do a 2.18.2 Documentation and Translations release and run with a 2.18.1 close to what we have. As far as I am concerned, the current state should be fine. We ought to be able to get translators, doc writers and other devs to help with catching

Re: Emergency call. Or not.

2014-02-16 Thread Trevor Daniels
David Kastrup wrote Sunday, February 16, 2014 2:45 PM I find that I'm currently dead-locking in decision-making with a somewhat tedieous task. Here is what it boils down to: basically git checkout -b translation origin/translation git log --reverse --no-merges origin/translation..origin

Re: Emergency call. Or not.

2014-02-16 Thread Jean-Charles Malahieude
Le 16/02/2014 16:18, Trevor Daniels disait : David Kastrup wrote Sunday, February 16, 2014 2:45 PM I find that I'm currently dead-locking in decision-making with a somewhat tedieous task. Here is what it boils down to: basically git checkout -b translation origin/translation git log

Re: Next buld

2014-02-16 Thread Phil Holmes
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: Devel lilypond-devel@gnu.org Sent: Saturday, February 15, 2014 12:14 PM Subject: Re: Next buld Phil Holmes m...@philholmes.net writes: 2.19.3 or 2.18.1? Time flies. When were you

Re: Doc: NR Clarify repeats w\ partials and barchecks (issue 61530043)

2014-02-16 Thread pkx166h
https://codereview.appspot.com/61530043/diff/20001/Documentation/notation/repeats.itely File Documentation/notation/repeats.itely (right): https://codereview.appspot.com/61530043/diff/20001/Documentation/notation/repeats.itely#newcode168 Documentation/notation/repeats.itely:168: measure,

Re: Authors.itexi - Updated Current Developers list (issue 61360043)

2014-02-16 Thread pkx166h
Reviewers: Graham Percival, fedelogy, Message: On 2014/02/15 09:34:06, fedelogy wrote: The Bug Squad list in Authors is out of date: http://lists.gnu.org/archive/html/bug-lilypond/2013-11/msg00138.html This list list should be also updated:

Re: Next buld

2014-02-16 Thread David Kastrup
Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: Devel lilypond-devel@gnu.org Sent: Saturday, February 15, 2014 12:14 PM Subject: Re: Next buld Phil Holmes m...@philholmes.net writes: 2.19.3

Re: line-breaking bug in 2.19

2014-02-16 Thread Janek Warchoł
Hi, 2014-01-17 17:55 GMT+01:00 Keith OHara k-ohara5...@oco.net: Starting with version 2.19.0, the bassoon part from http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=1793 gets a short line. The first commit where this happens is f8416b for issue 3304 (making horizontal spacing even)

Re: line-breaking bug in 2.19

2014-02-16 Thread Keith OHara
On Sun, 16 Feb 2014 13:58:01 -0800, Janek Warchoł janek.lilyp...@gmail.com wrote: 2014-01-17 17:55 GMT+01:00 Keith OHara k-ohara5...@oco.net: Starting with version 2.19.0, the bassoon part from http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=1793 gets a short line. I have tried to

Re: line-breaking bug in 2.19

2014-02-16 Thread Keith OHara
On Sun, 16 Feb 2014 17:33:16 -0800, Keith OHara k-ohara5...@oco.net wrote: On Sun, 16 Feb 2014 13:58:01 -0800, Janek Warchoł janek.lilyp...@gmail.com wrote: 2014-01-17 17:55 GMT+01:00 Keith OHara k-ohara5...@oco.net: Starting with version 2.19.0, the bassoon part from