Re: Use @dots{} instead of ... in notation manual where appropriate (issue 9964043)

lily...@orange.fr writes: > There is also > > notation/rhythms.itely:2320:If a manual beam is specified with > @code{[..]} set the beam Oh. That happens when you do search and replace on ... only. -- David Kastrup ___ lilypond-devel mailing list lil

Path to LilyPond 2.18

Hi folks, since the call for stabilization/freeze more or less in April, there has been quite a bit of work on finding and dealing with regressions. The amount that have cropped up there is really sobering. In particular with regard to circular dependencies, it looks like a whack-a-mole game wh

Re: Path to LilyPond 2.18

David Kastrup wrote Wednesday, June 05, 2013 5:07 PM > So for better or worse, we need to start wrapping up what we are going > to call our next stable release. > > I propose calling the next developer release 2.17.95 to send out the > message that finish-up work is called for: those translators

Re: Path to LilyPond 2.18

- Original Message - From: "David Kastrup" To: Cc: ; Sent: Wednesday, June 05, 2013 5:07 PM Subject: Path to LilyPond 2.18 Hi folks, since the call for stabilization/freeze more or less in April, there has been quite a bit of work on finding and dealing with regressions. [snip]

Re: Path to LilyPond 2.18

"Phil Holmes" writes: > From: "David Kastrup" >> I propose calling the next developer release 2.17.95 to send out the >> message that finish-up work is called for: > > I believe we need to get fixes for 3363 and 3386 into the code base > before cutting a release candidate. I was not talking abo

Re: Use @dots{} instead of ... in notation manual where appropriate (issue 9964043)

Le 04/06/2013 20:19, David Kastrup disait : lily...@orange.fr writes: There is also notation/rhythms.itely:2320:If a manual beam is specified with @code{[..]} set the beam Oh. That happens when you do search and replace on ... only. By the way, a git grep -n "\.\." > ../../../dblepoint.

Re: Use @dots{} instead of ... in notation manual where appropriate (issue 9964043)

Jean-Charles Malahieude writes: > Le 04/06/2013 20:19, David Kastrup disait : >> lily...@orange.fr writes: >> >>> There is also >>> >>> notation/rhythms.itely:2320:If a manual beam is specified with >>> @code{[..]} set the beam >> >> Oh. That happens when you do search and replace on ... only. >

Re: Path to LilyPond 2.18

> I'd prefer to declare 2.17.next_increment as a release candidate; let > that stand and if it's OK, cut 17.95 as a final RC, then run 2.18.0. Well, in emacs the first release candidate has .95, and I think this is a good decision. And I vote against a `final' RC; this makes too much pressure.

maybe we could use blog.lilypond.org as the blog's address?

Hi, from the previous discussion it seems that hosting our blog (currently lilypondblog.wordpress.com) on the same server as our website would be a bad idea and could lead to problems. I stand corrected. However, there seems to be another way of giving the blog a better "home" without impacting

Re: maybe we could use blog.lilypond.org as the blog's address?

Am 06.06.2013 00:09, schrieb Janek Warchoł: Hi, from the previous discussion it seems that hosting our blog (currently lilypondblog.wordpress.com) on the same server as our website would be a bad idea and could lead to problems. I stand corrected. However, there seems to be another way of givi

Re: Fixes problem with -dpreview cropping staff brackets (Issue 3386) (issue 9894043)

Patch set 3 from the original patch is not relevant. In the previous round of that review I had suggested marking the start brace as 'cross-staff' which generally means "my size/position/shape is not final until staves are spaced on the page". Unfortunately I forgot that 'cross-staff' has the

Re: Path to LilyPond 2.18

Phil Holmes philholmes.net> writes: > I believe we need to get fixes for 3363 and 3386 into the code base before > cutting a release candidate. Issue 3363, the scripts on cross-staff things being grossly misplaced, looks simple, but requires figuring out quite a lot of the sequencing of steps

PATCHES: Countdown for June 9 2013 - 06:00 GMT

Hello, *Countdown -- June 9 -- 06:00 GMT* * * * * * * * * 2948

Re: Path to LilyPond 2.18

On 6 juin 2013, at 06:52, Keith OHara wrote: > Phil Holmes philholmes.net> writes: > >> I believe we need to get fixes for 3363 and 3386 into the code base before >> cutting a release candidate. > > Issue 3363, the scripts on cross-staff things being grossly misplaced, > looks simple, but