On 2018-04-27 23:47, Ryan Schmidt wrote: > The repository permissions are deliberately set to prohibit force pushes that > change the history of master or release branches. Changing history causes > problems that we want to avoid.
I understand. That's why I said "depending on the repo and its settings". ;-) Disabling a forced push on master makes perfect sense. Just as a reference, the fastest way to do it: git revert --no-commit ad74231453^..24864aeda9 git commit -m "reverting commits ad74231453 to 24864aeda9" Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
signature.asc
Description: OpenPGP digital signature
