This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch zack/no-nested-includes in repository glibc.
discards ce2568bd5c Swap sys/poll.h with poll.h. discards 562c6a9083 Swap sys/syslog.h with syslog.h. discards d6fa230a3a Limit the set of strings.h functions also exposed in string.h. discards 7888495259 Don’t include sys/cdefs.h directly from public headers. discards 4494336f9a Don’t include sys/select.h from sys/types.h. discards 2fdb2dec07 Split up endian.h to minimize exposure of BYTE_ORDER. new be2515491a Split up endian.h to minimize exposure of BYTE_ORDER. new 2e7c120147 Don’t include sys/select.h from sys/types.h. new 4fcc0a149e Don’t include sys/cdefs.h directly from public headers. new 94dda58a95 Limit the set of strings.h functions also exposed in string.h. new 417fe2e3b3 Swap sys/syslog.h with syslog.h. new 7ff5af432a Swap sys/poll.h with poll.h.
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 (ce2568bd5c) \ N -- N -- N refs/heads/zack/no-nested-includes (7ff5af432a)
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: