glibc-ports-merge branch available for testing

["Joseph S. Myers" <joseph at codesourcery dot com>]

I've pushed the glibc-ports-merge branch that has the contents of the 
ports repository in the ports/ directory.  Please review this and see if 
it is as you expect.  There is a tag glibc-2.16-ports-merge at the tip of 
the branch; that tip revision is expected to become the tip of master if 
the merge is OK.

I followed the procedure described at 
<http://sourceware.org/glibc/wiki/Release/2.16/PortsMerge>, except that I 
moved .gitignore into the ports/ directory in the first part (preparing 
the checkout of the ports repository by moving files), rather than doing 
"git rm -f TMP/.gitignore" in the second part, so that the branch looks 
*exactly* like what you get from the two 2.16.0 release tarballs 
appropriately unpacked.  This ports/.gitignore can be removed along with 
ports/Banner and ports/Makefile once the merge is on master.

I've verified that the branch contents are indeed what you get from the 
release tarballs.  "git blame" works on files in ports.  "git log 
--follow" works on files where there isn't a file of the same name in 
libc; for files such as ports/Makefile it appears to prefer to show 
(before the move into the ports directory) the history of libc's file of 
that name rather than of the ports version.

-- 
Joseph S. Myers
joseph@codesourcery.com