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 3bd79168e1 ld: Create a new LOAD segment for -z textonly discards a2b1680e0d Update ldlang_check_relro_region/lang_find_relro_sections_1 discards 5e1b3e3c25 Add start and end of text-only region new 98b8ba312b Add start and end of text-only region new 05987d9f8e ld: Create a new LOAD segment for -z textonly

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 (3bd79168e1) \ N -- N -- N refs/heads/users/hjl/pr22393 (05987d9f8e)

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 2 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/scripttempl/elf.sc | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)