-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 After looking into filter-branch here is what I found out. from the docs: WARNING git filter-branch has a plethora of pitfalls that can produce non-obvious manglings of the intended history rewrite (and can leave you with little time to investigate such problems since it has such abysmal performance). These safety and performance issues cannot be backward compatibly fixed and as such, its use is not recommended. Please use an alternative history filtering tool such as git filter-repo. If you still need to use git filter-branch, please carefully read SAFETY (and PERFORMANCE) to learn about the land mines of filter-branch, and then vigilantly avoid as many of the hazards listed there as reasonably possible. ( https://git-scm.com/docs/git-filter-branch ) So here a git beginner, myself is cornered into navigating a "minefield". Illuminated language that git is full of undocumented known bugs. I see now what this facade of rejecting bugreports is about: it seem's about the bugreport recievers do dance around the jargon term "bug" in favor of various possibly more accurate 'illuminations' however as I have put in plain english a bug is a defect. -----BEGIN PGP SIGNATURE----- Version: ProtonMail wnUEARYKACcFgmc8+dYJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu 8pkAAAxwAP9ISjq2ja8Oc+BzmVTd39zFQ7G/fIuqRPvPhEoK9w5uIAD+Jtia wSnZYAEkEIPi7wAFU1wBhsgp6eU0Z5OMZhQM0Aw= =2LbM -----END PGP SIGNATURE-----
Attachment:
publickey - A_bughunter@proton.me - 0x66540805.asc
Description: application/pgp-keys
Attachment:
publickey - A_bughunter@proton.me - 0x66540805.asc.sig
Description: PGP signature
