i dont plan on suggesting any gcc-4.2 version for stable. arches of course are free to determine if gcc-4.2 works better for them than gcc-4.1 and thus move to stable.
gcc-4.3 seems to be standing up well. since the major gcc-ebuild-specific issues seem to be resolved now, i'll probably do a sweep of bugs to see if there's any patches i'm missing (if you guys know of a bug that should be addressed specifically in the gcc-4.3.0 ebuild, speak up now). then move on to the gcc 4.3 tracker bug (#198121). once this gets below a certain critical mass (i wont know what the critical mass is until it's been de-attained), then we'll be ~arching things. people are recommended to do a quick sweep of the lower hangers (many bugs have simple patches). i'll drop in ~ppc ~amd64 ~x86 as i use those every day. if any other arch is happy now with things, add your ~arch to the commented out list in cvs so i know to include it. -mike
signature.asc
Description: This is a digitally signed message part.
