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

unknown user pushed a change to branch hjl/cet/setjmp in repository glibc.

discards 67fec50189 Revert sysdeps/unix/sysv/linux/s390/longjmp_chk.c discards f97a11aa4b Remove generic __jmpbuf_arch_t.h and __saved_mask.h discards b41a64e6ed x86: Add paddings in jmpbuf for Intel CET new 71ac6d741e x86: Add paddings in jmpbuf for shadow stack pointer

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 (67fec50189) \ N -- N -- N refs/heads/hjl/cet/setjmp (71ac6d741e)

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 1 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: