Nerd. Tries to do the right thing.
Cares about cats, justice, transparency, and accessibility.
Helped make https://policepolicy.nz
If you'll be in Auckland on Saturday 13 June, make sure you're coming to this protest against NZ First's transphobic definitions bill
NZ First wrote their definitions bill after anti-trans hate group SUFW showed them a petition demanding such a bill. They gathered 2,245 signatures in 4 months
This petition *against* the bill just surpassed that in less than 4 hours ❤️
Please stand with us
Tonight I've published a reference document on the inspiration and history of NZ First's transphobic definitions bill. If you plan to make a submission, as I do, I hope this background can help you plan and write your submission
@forthy42@mastodon.net2o.de No .mailmap is visible to everone, it's a file in the repo. It would be visible only for you if you didn't commit it
It's true that it doesn't rewrite history, but in cases where rewriting history is not an option (commonly the case at work) then this is an option that doesn't require rewriting history
It's not perfect, and has downsides. But it may be the best option available in many cases
@tongpu@hachyderm.io I was looking today for a way to fix the way my old pre-transition commits show up in a git blame extension for VS Code, and this seems to work for that. I expect it works for other commands too but haven't tested a wide range
If you've changed your name, and you have old git commits that still show under your old name, you can fix it by adding a `.mailmap` file in the root of a git repository
This file lets you say what name and email address should appear any time git sees a particular email address for a commit author
