Don't we usually keep the revert message created by Git?

Looking at git log --grep='This reverts commit', there are two schools of thought on the question. Looking at our commit message guidelines, it doesn't say revert commits should be treated differently, so I'm going to leave the message as is, whoever lands this can choose a different commit message.

Looking at our commit message guidelines, it doesn't say revert commits should be treated differently

Our release tooling does have special treatment for the standard git revert message format. I’d rather edit our commit message guidelines to reflect that than ignore it 🙂 e.g. https://github.com/nodejs/node/blob/1d8a320a04d75b2143be0bc97b10dfcd9e64defa/doc/changelogs/CHANGELOG_V16.md#commits-3 contains

• [6af3e34b6b] - Revert "async_hooks: merge resource_symbol with owner_symbol" (Darshan Sen) #40741

Since this is a revert, is it reasonable to fast-track so it can be included in the 3rd May builds?

dont-land-on-v18.x

This PR and the on it reverts has the https://github.com/nodejs/node/labels/dont-land-on-v18.x, so none will be included on May 3rd release anyway :)

CI: https://ci.nodejs.org/job/node-test-pull-request/43881/

CI: https://ci.nodejs.org/job/node-test-pull-request/43885/

Landed in a3ff4bf