Re: items to verify for 2.15.36 - developers or active users requested

[-Eluze]

Phil Holmes-2 wrote:
> 
> "-Eluze" <address@hidden> wrote in message 
> news:address@hidden
>>
>> here is a list of issues to verify I can't handle:
>> http://old.nabble.com/file/p33653210/Fixed_2_15_36.png
>>
>> thanks
>> Eluze
> 
> You can, if you have time.  In the CG, it says:
> 
> Quite a few of these will be issues tracking patches. You do not have to 
> prove these patches work - simply that they have been pushed into the code 
> base. The developer should have put information similar to "Pushed as as 
> d8fce1e1ea2aca1a82e25e47805aef0f70f511b9" in the tracker. The long list of 
> letters and numbers is called the "committish". Providing you can find
> this 
> at the git tracker:
> 
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git
> then you should mark the issue as verified. A quick way of finding these
> is 
> to enter the committish at the following address:
> 
> http://philholmes.net/lilypond/git/
> 
> 
thanks - I did so, just leaving Issue 
https://code.google.com/p/lilypond/issues/detail?id=1690&can=7&q=Fixed_2_15_36&colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary
1690  because you wanted to apply another method for this and tbh I don't
know what I should exactly be looking for in tese docs!

Eluze
-- 
View this message in context: 
http://old.nabble.com/items-to-verify-for-2.15.36---developers-or-active-users-requested-tp33653210p33655940.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.