This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch hjl/pie/static in repository glibc.
discards 844ff726d1 Add --enable-static-pie to build-many-glibcs.py discards 145075991c Don't use hidden visibility in libc.a with PIE on i386 discards 3336d8e83b Add --enable-static-pie configure option to build static PIE new 7edd06916d Update sysdeps/unix/sysv/linux/ifaddrs.c new d5b617dac5 Add --enable-static-pie configure option to build static PIE new 03d0631c58 Don't use hidden visibility in libc.a with PIE on i386 new 1dc22c71a3 Add --enable-static-pie to build-many-glibcs.py
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (844ff726d1) \ N -- N -- N refs/heads/hjl/pie/static (1dc22c71a3)
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: ChangeLog | 6 ++++++ sysdeps/unix/sysv/linux/ifaddrs.c | 2 ++ 2 files changed, 8 insertions(+)