This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch aoliva/testme in repository gcc.
discards e1907ab640e [PR c++/85039] adjust context of new types in member initializers discards 26773d71bbe [PR c++/84979] reject auto in explicit tmpl args for tmpl-fn discards f787d39a78d [PR c++/84943] mark function as used when taking its address new 182643b0c2b [PR c++/84943] mark function as used when taking its address new 1235d425384 [PR c++/84979] reject auto in explicit tmpl args for tmpl-fn new e98ec638506 [PR c++/85039] adjust context of new types in member initializers
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 (e1907ab640e) \ N -- N -- N refs/heads/aoliva/testme (e98ec638506)
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/cp/decl2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)