This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch hjl/cet/master in repository glibc.
discards e407c46d7e x86-64: Check if Shadow Stack is enabled discards c0a5cc5ed4 Replace xorq with xorl discards 7efb0f3280 Add shadow stack pointer processing for Intel CET. discards c606c767e3 Linux/x86: Copy setjmp/longjmp for SHSTK discards b2fc38b796 x86: Support IBT and SHSTK in Intel CET [BZ #21598] discards a6aef6ef72 x86: Add feature_1 to tcbhead_t [BZ #22563] discards 3ea1e6c0d8 x86: Update cancel_jmp_buf to match struct __jmp_buf_tag [BZ [...] new 2e50ecd474 x86: Update cancel_jmp_buf to match struct __jmp_buf_tag [BZ [...] new 4f6f0b4ce3 x86: Add feature_1 to tcbhead_t [BZ #22563] new c8006c7f56 x86: Support IBT and SHSTK in Intel CET [BZ #21598] new b9437f0801 Linux/x86: Copy setjmp/longjmp for SHSTK new 175635e387 Add shadow stack pointer processing for Intel CET. new cd364da869 Replace xorq with xorl new 05ec10fbe5 x86-64: Check if Shadow Stack is enabled
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 (e407c46d7e) \ N -- N -- N refs/heads/hjl/cet/master (05ec10fbe5)
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 7 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: