On 2011/11/03 13:15:23, J_lowe wrote:
http://codereview.appspot.com/5306076/diff/3002/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (left):
http://codereview.appspot.com/5306076/diff/3002/Documentation/notation/changing-defaults.itely#oldcode732
Documentation/notation/changing-defaults.itely:732: The @code{\Staff
\RemoveEmptyStaves} will overwrite your current
On 2011/11/03 13:05:21, dak wrote:
> On 2011/11/03 12:27:33, Neil Puttock wrote:
> > This knownissue no longer applies.
>
> Not exactly my fault. Since I have no clue how much material needs
to get
> removed here, and whether it needs to be replaced by something else,
I prefer
> leaving that change to someone else.
>
> I don't see a reason why this should block my patch: surely
correcting one
error
> is better than correcting none.
Can you just remove everything between
@knownissues all the way down to (but not including) @c TODO when you
push?
I don't think that would be a big deal.
James
Pushed something to dev/staging doing that. This should teach me to do
"fast fixes".
http://codereview.appspot.com/5306076/
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
