This is an automated email from the git hooks/post-receive script.

unknown user pushed a change to branch zack/headers-cleanups in repository glibc.

discards 717d9c5f41 Remove __need_schedparam and __cpu_set_t_defined. discards 3203b3912f Remove __need_IOV_MAX and __need_FOPEN_MAX. discards ac5f3f3984 Remove __need macros from stdio.h and wchar.h. discards e0c0d1bed7 Remove __need macros from errno.h (__need_Emath, __need_error_t). new 2cdfa9e848 Add one more header to be installed, missed from previous patch. new f3ee1ac681 Remove __need macros from errno.h (__need_Emath, __need_error_t). new 5b32430cd8 Remove __need macros from stdio.h and wchar.h. new 81e1d8634f Remove __need_IOV_MAX and __need_FOPEN_MAX. new cab998f402 Remove __need_schedparam and __cpu_set_t_defined.

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 (717d9c5f41) \ N -- N -- N refs/heads/zack/headers-cleanups (cab998f402)

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 5 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 | 4 ++++ signal/Makefile | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-)