Re: bug report format change

2004-08-22 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > On Sunday 22 August 2004 13.28, Han-Wen Nienhuys wrote: > > Hi Eric, > > > > the bug collection has gotten rather large, and difficult for me to > > get an overview of. To help things, I'm adding a .ly -> .tely -> .texi > > -> conversion and a GNUmakefile, so I can get a

Re: bug report format change

2004-08-22 Thread Erik Sandberg
On Sunday 22 August 2004 13.28, Han-Wen Nienhuys wrote: > Hi Eric, > > the bug collection has gotten rather large, and difficult for me to > get an overview of. To help things, I'm adding a .ly -> .tely -> .texi > -> conversion and a GNUmakefile, so I can get a neat .HTML with > images, containing

Re: bug report format change

2004-08-22 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > Creating a makefile is a very good idea. I'm actually losing overview myself, > as well. > > Hm - while you are at it: Notice the format of the two first lines of each > file. The first line is a list of flags, the second line is a CC: field; > changes in the bug

Re: bug report format change

2004-08-22 Thread Erik Sandberg
On Sunday 22 August 2004 13.28, Han-Wen Nienhuys wrote: > Hi Eric, > > the bug collection has gotten rather large, and difficult for me to > get an overview of. To help things, I'm adding a .ly -> .tely -> .texi > -> conversion and a GNUmakefile, so I can get a neat .HTML with > images, containing

bug report format change

2004-08-22 Thread Han-Wen Nienhuys
Hi Eric, the bug collection has gotten rather large, and difficult for me to get an overview of. To help things, I'm adding a .ly -> .tely -> .texi -> conversion and a GNUmakefile, so I can get a neat .HTML with images, containing the status of all bugs. To make this feasible, the syntax of a lo