EGLIBC (was: GNU C Library development and maintainers)

[Joseph S. Myers]

Also, a concrete suggestion regarding merging the small, self-contained 
miscellaneous changes: if you find a change that only affects one of two 
files, doesn't depend on other EGLIBC changes and doesn't involve tricky 
design issues, but aren't going to merge it yourself straight away, it may 
make sense to create an issue in glibc Bugzilla, with pointers to the 
original patches@eglibc.org discussion of the change, any discussion of 
followup changes, and the original and any followup commits, and give that 
issue a new "eglibc-merge" keyword.  Such miscellaneous changes are a lot 
closer to being usefully identifiable and mergeable from individual 
commits than the larger changes, though you do still in all cases need to 
look for followup fixes and find the original discussion giving the 
rationale for the change.

(There are such changes in ports as well as libc - some m68k/ColdFire 
changes at least - so I don't think attention should be restricted to libc 
when looking for small changes that might be merged.)

-- 
Joseph S. Myers
joseph@codesourcery.com