Re: Issue 722 in lilypond: newline inside @macro{} in texinfo screws up

[Graham Percival]

On Sun, Jan 11, 2009 at 12:10:49PM +0000, address@hidden wrote:
>
> Comment #1 on issue 722 by v.villenave: newline inside @macro{} in 
> texinfo screws up
> http://code.google.com/p/lilypond/issues/detail?id=722
>
> Perhaps we could have a dedicated Type label for such bugs, such as 
> "Type-Docbug"?

Type-Other is sufficient.  There's no point inventing
Type-Buildsystem, Type-Translation-Infrastructure,
Type-CG-instructions, Type-Fontengine, Type-Code-Style, etc.

The idea is simply to avoid the evilness of personal TODO lists:
unless you're certain that you'll handle something within two
weeks, add it to the tracker so it doesn't get lost.  I don't
anticipate a huge number of Type-Other items.

Cheers,
- Graham