This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch users/aburgess/gdb-opt-code-debug in repository binutils-gdb.
discards 90dad0d29b7 [wip] Fix range end handling of inlined subroutines discards 4a495f451cb [wip] Introduce a new line table flag is_weak discards 7e17a55b788 [wip] gdb/testsuite: all the optimised code test cases discards 49f425d5e82 gdb: improve line number lookup around inline functions discards a8c9c41aa71 gdb: handle empty ranges for inline subroutines new 9d3050f16a5 gdb: handle empty ranges for inline subroutines new a44b897c11e gdb: improve line number lookup around inline functions new 17e78553102 [wip] gdb/testsuite: all the optimised code test cases new 566da9a1da8 [wip] Introduce a new line table flag is_weak new 1bf19d6af01 [wip] Fix range end handling of inlined subroutines
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 (90dad0d29b7) \ N -- N -- N refs/heads/users/aburgess/gdb-opt-code-debug (1bf19d6af01)
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: