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

unknown user pushed a change to branch users/hjl/pr22393 in repository binutils-gdb.

discards 867cf7c85f x86-64: Add tests for -z textonly -z max-page-size=0x1000 discards 983c940c8e ld: Add tests for -z textonly and -z notextonly discards 611c9f89e0 ld/ppc/spu: Also set expld.textseg.phase to exp_seg_none discards c4f8600417 ld: Create a new LOAD segment for text-only LOAD segment discards d6d9d7d077 ld: Add TEXT_SEGMENT_ALIGN/TEXT_SEGMENT_{RELRO_}END discards 233e943ba4 ld: Add "-z textonly" option to ELF linker new 10728c17a5 ld: Add "-z textonly" option to ELF linker new e7528d0119 ld: Add TEXT_SEGMENT_ALIGN/TEXT_SEGMENT_{RELRO_}END new cc2bcf6271 ld: Create a new LOAD segment for text-only LOAD segment new ab0d66f33a ld/ppc/spu: Also set expld.textseg.phase to exp_seg_none new 3eab3df181 ld: Add tests for -z textonly and -z notextonly new 6a98c098b8 x86-64: Add tests for -z textonly -z max-page-size=0x1000

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 (867cf7c85f) \ N -- N -- N refs/heads/users/hjl/pr22393 (6a98c098b8)

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: ld/lexsup.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)