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

unknown user pushed a change to branch users/helflym/try-aarch64nto in repository binutils-gdb.

discards 09ef1011a96 ld/testsuite: adjust ld-aarch64 tests for aarch64nto address discards 43b711ffa8a ld/testsuite: adjust tests dump to handle _btext on aarch64-qnx discards ea1e72ca705 ld/testsuite: disable ilp32 tests for aarch64-qnx discards 38d02711c43 ld/testsuite: add aarch64nto to ld-aarch64 discards 6fbce2675c2 ld: add support of QNX stack arguments for aarch64nto new a6c460631af ld: add support of QNX stack arguments for aarch64nto new 50830a3c008 ld/testsuite: add aarch64nto to ld-aarch64 new 6d9fb23e881 ld/testsuite: disable ilp32 tests for aarch64-qnx new 06bc164e6c7 ld/testsuite: adjust tests dump to handle _btext on aarch64-qnx new 4bb646c3990 ld/testsuite: adjust ld-aarch64 tests for aarch64nto address

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 (09ef1011a96) \ N -- N -- N refs/heads/users/helflym/try-aarch64nto (4bb646c3990)

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 5 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/emultempl/nto.em | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-)