Two further points:
* As a reminder, the glibc-2.16-ports-merge tag represents the union of
libc and ports 2.16, so you can for example do "git shortlog
glibc-2.16-ports-merge..HEAD" to see changes made for 2.17 development.
* Nothing has so far changed about how ports is developed beyond the use
of a subdirectory in the libc repository. Thus, ports changes still go to
the libc-ports mailing list and still use the separate ports ChangeLogs,
and developers are not required to update ports in global changes
(although they are certainly welcome to do so, and should try to identify
where ports changes are needed if they didn't make them) unless and until
we decide to change such things.
--
Joseph S. Myers
joseph@...
