Re: Git problem

[Phil Holmes]

----- Original Message ----- 
From: "Phil Holmes" <address@hidden>
To: "Peekay" <address@hidden>; "Colin Hall" <address@hidden>; 
"Eluze" <address@hidden>; "Marek Klein" <address@hidden>; "Ralph 
Palmer" <address@hidden>
Cc: "Graham Percival" <address@hidden>; <address@hidden>
Sent: Thursday, March 08, 2012 4:46 PM
Subject: Git problem


> If you read .devel, you will have seen that there was a major problem with 
> git.  As a result, we're not 100% sure that all the fixes verified for 
> 15.31 and 15.32 are still in the build.  I'm going through all the 
> possible problem issues reverting Verified to Fixed.  The safest was to 
> re-verify will be to check the source as pulled from master to ensure that 
> the text shown as changed in the patch has actually appeared in the source 
> code.  If you're not comfortable doing this, please leave them as "fixed" 
> status and those of us who are can work our way through.
>
> Graham - you may want to hold a further release just because of the 
> uncertainty, but give us a while to work through these.


One thought.  Some issues are best verified by checking lily output - 
http://code.google.com/p/lilypond/issues/detail?id=2246 for example.  Can we 
break a normal rule and check these against a newly made binary?  What we'd 
then be doing is saying "it was in the GUB binary and is still in master, so 
I'm going to verify".

--
Phil Holmes