Moving ports architectures to libc?

[Joseph S. Myers]

I have now tagged architecture-specific bugs outside of the ports 
component along the lines I suggested - [i386], [powerpc] etc. in the bug 
titles and Host set accordingly.  I also moved various bugs to other 
components, closed bugs etc. as seemed appropriate.  Please fix any 
mistakes you see, or bugs I failed to tag.  My suggestion for bugs in the 
ports component is that they should be tagged and have Host set if needed 
at the point where they are moved to another component, when the port in 
question is moved to the main sysdeps directory.

We still need more people working on bugs, including helping to confirm if 
old bugs are still present / are valid non-duplicate bugs, putting them in 
appropriate components, tagging, going through past bugs fixing them, and, 
where there is controversy over whether something is a bug / whether a 
proposed new feature is desirable, taking it to libc-alpha and trying to 
drive the consensus process to a conclusion.  When I started working 
through "math" bugs a couple of years ago, I hoped that other people would 
similarly work through open bugs in other areas (including the catch-all 
"libc", where maybe there are still things that could be split out into 
new components) and become the glibc experts in those areas.  We have 
Chris doing some of this for "localedata", but other areas still need such 
work on their bugs.

-- 
Joseph S. Myers
joseph@codesourcery.com