Patrick McCarty | 1 Jan 01:10 2010
Picon

Re: Multi-line titles lose text in 2.13.10

On Thu, Dec 31, 2009 at 12:20 PM, Patrick McCarty <pnorcks <at> gmail.com> wrote:
> On Thu, Dec 31, 2009 at 12:13 PM, Graham Percival
> <graham <at> percival-music.ca> wrote:
>> On Thu, Dec 31, 2009 at 12:07:03PM -0800, Patrick McCarty wrote:
>>> This warning appears to be a problem introduced (by me) when mbrtowc()
>>> was removed.  This happened before 2.13.8.  The problem disappears
>>> when the CR/LF line endings are changed to LF.
>>>
>>> Once I figure out why CR/LF line endings in markup are handled
>>> incorrectly, I'll push a fix.
>>
>> Do you think this should delay 2.13.10 ?  If you think it'll be a
>> quick fix, I'm willing to wait a day or two.
>
> Yes.  I'll try to fix it ASAP.

Okay, my most recent commit (a19685ed8278fc55276bcb609f7ac862c1cbe3d5)
should fix this problem.

Thanks,
Patrick
lilypond | 1 Jan 03:41 2010

Re: Issue 954 in lilypond: GUB add temporary patch to lilypond


Comment #2 on issue 954 by percival.music.ca: GUB add temporary patch to  
lilypond
http://code.google.com/p/lilypond/issues/detail?id=954

Hmm.  We just finished fixing GUB to work with building from branches, so  
this idea
definitely has appeal.  Also, if we do this, then the branch-specific  
builds will get
used+tested all the time, so we'll notice much sooner if it breaks again.

Plus, this would let translators update news-front before we make the  
release.  I
can't see anybody caring for 2.13.10, but I'm sure they'd like to do that  
for 2.14.0.

Ok, I'll go with this.  At the moment, I'm envisioning a release/unstable  
branch;
just before I want to make a release, I'll pull everything from master into  
it.  I
can add the news item and update the VERSION, do the gub stuff, then  
cherry-pick
those commits back into master.  Is that what you had in mind?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
(Continue reading)

lilypond | 2 Jan 00:16 2010

Re: Issue 954 in lilypond: GUB add temporary patch to lilypond


Comment #3 on issue 954 by hanwenn: GUB add temporary patch to lilypond
http://code.google.com/p/lilypond/issues/detail?id=954

I had a branch of my own that never left my machine.  I build GUB from
localhost:/home/hanwen/vc/lilypond, branch=master, and would add local  
commits there
to fix things up for the release. The point of making the branch local is  
that nobody
pushes to it unexpectedly (potentially triggering expensive and non QA-ed  
builds)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
lilypond | 2 Jan 10:24 2010

Re: Issue 885 in lilypond: Uninstallation issues

Updates:
	Status: Started
	Owner: pnorcks

Comment #1 on issue 885 by pnorcks: Uninstallation issues
http://code.google.com/p/lilypond/issues/detail?id=885

I think we should open separate issues for every uninstallation problem.   
Then it's
easier to keep track of which ones are actually fixed.

This issue has a pending fix (hopefully).

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
lilypond | 2 Jan 10:34 2010

Re: Issue 755 in lilypond: SVG backend improvements

Updates:
	Status: Fixed
	Owner: pnorcks
	Labels: fixed_2_13_4

Comment #2 on issue 755 by pnorcks: SVG backend improvements
http://code.google.com/p/lilypond/issues/detail?id=755

All of the above problems were fixed before 2.13.4 was released, so I'm  
going to
close this issue.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
lilypond | 2 Jan 10:51 2010

Re: Issue 901 in lilypond: gub: lilypad.exe has a 40% chance of being included


Comment #4 on issue 901 by pnorcks: gub: lilypad.exe has a 40% chance of  
being included
http://code.google.com/p/lilypond/issues/detail?id=901

Is this fixed now, Graham?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
lilypond | 2 Jan 11:53 2010

Re: Issue 901 in lilypond: gub: lilypad.exe has a 40% chance of being included

Updates:
	Status: Fixed
	Labels: fixed_2_13_10

Comment #5 on issue 901 by percival.music.ca: gub: lilypad.exe has a 40%  
chance of being included
http://code.google.com/p/lilypond/issues/detail?id=901

Thanks, I meant to indicate this after 2.13.10 was out, but I forgot.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
lilypond | 2 Jan 11:57 2010

Re: Issue 885 in lilypond: Uninstallation issues


Comment #2 on issue 885 by percival.music.ca: Uninstallation issues
http://code.google.com/p/lilypond/issues/detail?id=885

I agree; one issue per issue.  Fortunately, in this case we only had one  
problem (the
extra symlinks).

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
lilypond | 2 Jan 12:13 2010

Re: Issue 945 in lilypond: warning about \version for short snippets

Updates:
	Status: Fixed
	Labels: fixed_2_13_10

Comment #4 on issue 945 by v.villenave: warning about \version for short  
snippets
http://code.google.com/p/lilypond/issues/detail?id=945

I think these additions to the LM are great. I'm marking this as Fixed,  
unless
someone wants to implement Graham's #3 proposal (in which case i'll reopen  
this).

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
lilypond | 2 Jan 12:18 2010

Re: Issue 904 in lilypond: Regression: partially-tied chords may look wrong when the tie flips

Updates:
	Labels: -Priority-Regression Priority-Medium Engraving-nitpick

Comment #2 on issue 904 by v.villenave: Regression: partially-tied chords  
may look wrong when the tie flips
http://code.google.com/p/lilypond/issues/detail?id=904

OK. But it's still not perfect :)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

Gmane