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

unknown user pushed a change to branch nsz/pacbti-v5 in repository glibc.

discards bf6dffdb8a aarch64: add NEWS entry about branch protection support discards aff20456ec aarch64: redefine RETURN_ADDRESS to strip PAC discards e5d729bd16 aarch64: fix pac-ret support in _mcount discards ec99013029 aarch64: Add pac-ret support to assembly files discards 140ba3e772 aarch64: configure check for pac-ret code generation discards b8dd3fb10a aarch64: enable BTI at runtime new efb1131acc aarch64: enable BTI at runtime new 660c83073d aarch64: configure check for pac-ret code generation new abdae6d290 aarch64: Add pac-ret support to assembly files new 8f62ca7328 aarch64: fix pac-ret support in _mcount new 6d42e5c220 aarch64: redefine RETURN_ADDRESS to strip PAC new 27ba4dcee8 aarch64: add NEWS entry about branch protection support

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 (bf6dffdb8a) \ N -- N -- N refs/heads/nsz/pacbti-v5 (27ba4dcee8)

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: