Wait, what's the preferred way of reverting a patch? I followed what I saw in:
commit 04ee1f788ceaa4c7f777ff3b9441ae076191439c
Author: Jeff Law <j...@ventanamicro.com>
Date: Mon May 13 21:42:38 2024 -0600
Revert "[PATCH v2 1/3] RISC-V: movmem for RISCV with V extension"
This reverts commit df15eb15b5f820321c81efc75f0af13ff8c0dd5b.
and here:
commit 0c6dd4b0973738ce43e76b468a002ab5eb58aaf4
Author: YunQiang Su <s...@debian.org>
Date: Mon May 13 14:15:38 2024 +0800
Revert "MIPS: Support constraint 'w' for MSA instruction"
This reverts commit 9ba01240864ac446052d97692e2199539b7c76d8.
and here:
commit f6ce85502eb2e4e7bbd9b3c6c1c065a004f8f531
Author: Hans-Peter Nilsson <h...@bitrange.com>
Date: Wed May 8 04:11:20 2024 +0200
Revert "Revert "testsuite/gcc.target/cris/pr93372-2.c: Handle
xpass from combine improvement""
This reverts commit 39f81924d88e3cc197fc3df74204c9b5e01e12f7.
etc etc.
Next time, would you like me to add manual changelog entries?
My apologies, I thought what I did was the blessed way of doing things.
Aldy
On Thu, May 16, 2024 at 12:08 PM Jakub Jelinek <ja...@redhat.com> wrote:
>
> On Thu, May 16, 2024 at 12:01:01PM +0200, Aldy Hernandez wrote:
> > This reverts commit d7bb8eaade3cd3aa70715c8567b4d7b08098e699 and enables
> > prange
> > support again.
>
> Please don't do this.
> This breaks ChangeLog generation, will need to handle it tomorrow by hand
> again.
> Both the ammendments to the git (cherry-pick -x or revert) added message
> lines
> This reverts commit COMMITHASH.
> and
> (cherry picked from commit COMMITHASH)
> and revert of revert.
>
> Jakub
>
