Although this particular change doesn't affect me - rewriting history is a bad idea.

Why not simply commit a revert back to a cleaner point on "master" branch and then commit the new changes you want from there?

Then history is not lost on master branch.

Or, with the BLM movement some repos are stopping use of master branch. github seems to be encourage it going forware: https://www.zdnet.com/article/github-to-replace-master-with-alternative-term...

So another option: stop using "master" branch. You could even create a tag/rename and then delete the branch name to avoid any confusions. History won't be rewritten then, just a little "hidden". And start using a new "main" branch. You can push you entire commit series there without revering anything on master branch.

Regards, Scott

-----Original Message----- From: Mbed-tls-announce [mailto:mbed-tls-announce-bounces@lists.trustedfirmware.org] On Behalf Of Janos Follath via Mbed-tls-announce Sent: Thursday, July 16, 2020 4:09 AM To: mbed-tls-announce@lists.trustedfirmware.org Cc: nd nd@arm.com Subject: [Mbed-tls-announce] Force push on the master branch

Hi All,

The master branch used to track the latest development release. This changed in early 2019 after the 2.16 LTS branch was released. Around this time the cryptography library of Mbed TLS was moved to a separate repository and since then it was used as a submodule. This was one of the main reasons behind the decision to keep master pointing to the 2.16 LTS releases.

Recently we have merged the cryptography library back into Mbed TLS. We don't have any reasons any more to keep master tracking the 2.16 LTS release. Therefore we intend to update master to the latest development release. This will happen on 3rd August.

The update will involve a force push, which can be disruptive to those users who take Mbed TLS from master. We would like to give such users enough time to adapt to this change. If you are relying on the master branch in a way that this force push affects you, please let us know on the developer mailing listhttps://lists.trustedfirmware.org/mailman/listinfo/mbed-tls and we will do our best to accommodate your needs.

Thanks and regards,

Janos (on behalf of the Mbed TLS maintainer team)

-- Mbed-tls-announce mailing list Mbed-tls-announce@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/mbed-tls-announce