Re: Bugzilla components for target libraries

2011-11-14 Thread Matthias Klose
On 11/10/2011 06:30 PM, Joseph S. Myers wrote: > On Thu, 10 Nov 2011, Rainer Orth wrote: > >> I've recently noticed that several of our target libraries are not >> properly (if at all) represented as bugzilla components. The following >> table shows the current situation: >> >> directory

Re: Bugzilla components for target libraries

2011-11-10 Thread Ian Lance Taylor
Rainer Orth writes: > The entries in parens are only covered indirectly and may or may not > warrant their own components. I'd argue that it would be helpful to > have libada and libgo components of their own (while libcpp would > probably be overkill), but of course that's ultimately up to the

Re: Bugzilla components for target libraries

2011-11-10 Thread Joseph S. Myers
On Thu, 10 Nov 2011, Rainer Orth wrote: > I've recently noticed that several of our target libraries are not > properly (if at all) represented as bugzilla components. The following > table shows the current situation: > > directory component You omitted boehm-gc and zlib, both used

Re: Bugzilla components for target libraries

2011-11-10 Thread Torvald Riegel
On Thu, 2011-11-10 at 14:22 +0100, Rainer Orth wrote: > I think that at least some of the gaps need to be filled, notably libgcc > (recently bugs have been filed under other), libitm (new with the > trans-mem merge, but fits nowhere else) Something for libitm would probably make sense (or "trans-m

Re: Bugzilla components for target libraries

2011-11-10 Thread Arnaud Charlet
> I think we should have different components only if we have different > maintainers for them (or, if they do not naturally belong to another > component). Right, precisely for Ada that would be the same set of people. > Note that most bug submitters confuse the bug component with the > language

Re: Bugzilla components for target libraries

2011-11-10 Thread Richard Guenther
On Thu, Nov 10, 2011 at 2:35 PM, Arnaud Charlet wrote: >> The entries in parens are only covered indirectly and may or may not >> warrant their own components.  I'd argue that it would be helpful to >> have libada and libgo components of their own (while libcpp would >> probably be overkill), but

Re: Bugzilla components for target libraries

2011-11-10 Thread Arnaud Charlet
> The entries in parens are only covered indirectly and may or may not > warrant their own components. I'd argue that it would be helpful to > have libada and libgo components of their own (while libcpp would > probably be overkill), but of course that's ultimately up to the > respective maintaine