What is the current established way of reverting a patch, with the current state of the tools?
I did $ git revert r9-8541-g2a732dbdfcc0a3bc2b4bdb5387fffa193fea6df6 on origin/releases/gcc-9, and now only the ChangeLog entries reversed (which is not wanted), but the code is unchanged (which is even less wanted). And, if somebody figures it out, please also update https://gcc.gnu.org/gitwrite.html . Regards Thomas (Here is what I will _not_ push :-) $ git diff HEAD^1 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 3e7f3c76360..a3b279b602d 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -54,15 +54,6 @@ * expr.c (gfc_check_pointer_assign): Revert patch for PR 93956. * interface.c: Likewise. -2020-04-24 Thomas Koenig <tkoe...@gcc.gnu.org> - - Backport from trunk - PR fortran/93956 - * expr.c (gfc_check_pointer_assign): Also set subref_array_pointer - when a function returns a pointer. - * interface.c (gfc_set_subref_array_pointer_arg): New function. - (gfc_procedure_use): Call it. - 2020-04-20 Harald Anlauf <anl...@gmx.de> Backport from mainline. diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 667a1edefea..452fa1d1958 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -150,20 +150,6 @@ PR target/93654 * gcc.target/i386/pr93654.c: New test. -2020-04-24 Thomas Koenig <tkoe...@gcc.gnu.org> - - Backport from trunk - PR fortran/93956 - * gfortran.dg/pointer_assign_13.f90: New test. - -2020-04-23 Iain Sandoe <i...@sandoe.co.uk> - - * g++.dg/coroutines/coro-bad-alloc-00-bad-op-new.C: Adjust for - changed inline namespace. - * g++.dg/coroutines/coro-bad-alloc-01-bad-op-del.C: Likewise. - * g++.dg/coroutines/coro-bad-alloc-02-no-op-new-nt.C: Likewise - * g++.dg/coroutines/coro.h: Likewise - 2020-04-21 Martin Sebor <mse...@redhat.com> PR c++/94510
