This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch aoliva/SLI in repository gcc.
discards 6e1a3b94d83 Statement Frontier Notes, Location Views, and Inlined Entry [...] discards 86dedf8ed0d [IEPM] Introduce inline entry point markers discards 12521ac379a [IEPM] Introduce debug hook for inline entry point markers discards e097183372d [LVU] Introduce location views new 41f1596ecd3 [LVU] Introduce location views new b5fd4a3ba3a [IEPM] Introduce debug hook for inline entry point markers new d0b4c085c15 [IEPM] Introduce inline entry point markers
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 (6e1a3b94d83) \ N -- N -- N refs/heads/aoliva/SLI (d0b4c085c15)
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 3 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: gcc/dwarf2out.c | 13 +++++++++++++ gcc/final.c | 1 - 2 files changed, 13 insertions(+), 1 deletion(-)