Re: Libtool head tests: compiler_c_o and inherited linker flags

[Gary V. Vaughan]

Hallo Ralf,

On 26 Aug 2005, at 13:05, Ralf Wildenhues wrote:
> at the time of writing it I knew it, too, but then forgot to fix  
> it; oh
> well, yet another reason for a central bug list/repository

This is working quite nicely now:

http://tkd.kicks-ass.net/GnuLibtoolProject/BugReports
http://tkd.kicks-ass.net/GnuLibtoolProject/FeatureRequests
http://tkd.kicks-ass.net/GnuLibtoolProject/ToDo

I'll put up some documentation on how to use it shortly, but it  
effectively allows
us to submit issues to any of these pages from the Create form near  
the bottom of
each page; they are assigned a unique issue number that we can use to  
refer to them
(like the PR/foo of automake's tracker); and the pages that are  
pertinent will keep
automatic track of lists of issues by project|scheduled release|issue  
status... the
http://tkd.kicks-ass.net/GnuLibtoolProject/RoadMap page (among  
others) now has an
issue search box, so entering (say) 2 and clicking the show button  
takes you directly
to that issue.

There's more to come, but let's put release 2.0 out the door first ;-)

(and of course, if adding a whole new page for something seems like  
too much trouble,
there is still the long list of stuff in RoadMap)

Cheers,
    Gary.
--
Gary V. Vaughan      ())_.  gary@ 
{lilith.warpmail.net,gnu.org},address@hidden
Research Scientist   ( '/   http://www.tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/{libtool,m4}
Technical Author   `(_~)_   http://sources.redhat.com/autobook

PGP.sig
Description: This is a digitally signed message part