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 1e36b53e063 [PR86747] tsubst friend tpl ctxt before looking it up for dupes discards cb0f0107b4e [PR87012] canonicalize ref type for tmpl arg new ac88769d417 [PR87012] canonicalize ref type for tmpl arg new e0ca29338bb [PR86747] tsubst friend tpl ctxt before looking it up for dupes new 98469668489 [PR86823] retain deferred access checks from outside firewall
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 (1e36b53e063) \ N -- N -- N refs/heads/aoliva/testme (98469668489)
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/parser.c | 5 ++++- gcc/testsuite/g++.dg/cpp0x/pr87012.C | 2 ++ gcc/testsuite/g++.dg/pr86823.C | 15 +++++++++++++++ 3 files changed, 21 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/g++.dg/pr86823.C