bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 2286 in lilypond: Patch: Make #{ c' #} and x=c' create a pitch


From: lilypond
Subject: Re: Issue 2286 in lilypond: Patch: Make #{ c' #} and x=c' create a pitch instead of a NoteEvent
Date: Mon, 13 Feb 2012 16:05:12 +0000


Comment #8 on issue 2286 by address@hidden: Patch: Make #{ c' #} and x=c' create a pitch instead of a NoteEvent
http://code.google.com/p/lilypond/issues/detail?id=2286

Technically we just check that the commit is in git, not that the commit is in a particular branch. We cannot expect bug squad members to have that level of familiarity with git; if he can find that commit in git right now, he'll still find it in git a few days from now. Yes, this means that a patch could still get lost (i.e. if the commit is in somebody's dev/ branch and never pushes it to staging), but that's simply an acceptable risk at the moment.

However, also technically, nothing marked fixed_2_15_30 should be verified until the official 2.15.30 GUB release. So I agree with moving this back to Fixed, but not for the reason that David suggested.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]