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 92506a1b7d ASFLAGS-.o += $(pie-default) discards a04696ccaa Add --enable-static-pie to build-many-glibcs.py discards c72dd4cf1e sparc: Check PIC instead of SHARED in start.S discards 98fcde69d9 microblaze: Check PIC instead of SHARED in start.S discards 8c67340614 sh: Update elf_machine_load_address for static PIE discards fe9e9174f5 s390: Update elf_machine_load_address for static PIE discards 17b9efc649 Add --enable-static-pie configure option to build static PIE [...] new 2cdcd22264 Add --enable-static-pie configure option to build static PIE [...] new e2b24b533b s390: Update elf_machine_load_address for static PIE new b58a130b0e sh: Update elf_machine_load_address for static PIE new fee70a13ae microblaze: Check PIC instead of SHARED in start.S new a83f5a663e sparc: Check PIC instead of SHARED in start.S new 1d043a3760 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 (92506a1b7d) \ N -- N -- N refs/heads/hjl/pie/static (1d043a3760)
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 6 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: Makeconfig | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)