Re: Issue 2018 in lilypond: Patch: parser.yy: allow postevents in function arguments in general

[lilypond]

Updates:
        Labels: -Patch-needs_work Patch-new

Comment #4 on issue 2018 by address@hidden: Patch: parser.yy: allow  
postevents in function arguments in general
http://code.google.com/p/lilypond/issues/detail?id=2018

I don't particularly like "Patch-needs_work: Review has identified some  
problems" status when the only "problem" is that the patch is based (and  
consequently blocked) on another patch.

It keeps people from reviewing the patch, and the whole point of uploading  
it was getting it reviewed.  So I am flagging this as Patch-new again.  If  
that triggers some automatic procedure that fails, we need to redesign our  
procedures.  "Blocked on" should be considered similar to "Needs_work"  
regarding the progression of automatic testing.

Of course, it would be even nicer if the patch _was_ tested on top of the  
blocking issue patch whenever the blocking issue patch moves to  
Patch-review, but that would also mean that this patch gets back  
to "Patch-new" whenever the blocking issue gets an updated patch.  Complex.