PEP 561, 759, 777: Update my name, email, and links

[emmatyping]

• Change is either:
  • To a Draft PEP
  • To an Accepted or Final PEP, with Steering Council approval
  • To fix an editorial issue (markup, typo, link, header, etc)
• PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

I wasn't sure whether this is classified as a meta change or an editorial change, so I just chose editorial.

---

📚 Documentation preview 📚: https://pep-previews--4229.org.readthedocs.build/

[hauntsaninja]

Btw, when merging this I noticed your commits are still authored under the previous email

[emmatyping]

Thank you for merging!

I noticed your commits are still authored under the previous email

Yeah, I'm not sure if there is much to be done there without rewriting history, right?

[hauntsaninja]

Sorry, I meant new commits, like the one in this PR. See e.g. https://github.com/python/peps/commit/3cf28aa6675e419e5da861b52788bf10ff4abdef.patch
(I don't know of a viable way to change old commits)

[emmatyping]

Ahh, thank you for pointing that out! I was using an old server I hadn't updated yet

[hugovk]

Yeah, I'm not sure if there is much to be done there without rewriting history, right?

It's somewhat possible by adding a .mailmap file to the repo like:

Emma Smith <new@example.com> <old@example.com>

For example:

• https://ntietz.com/blog/git-mailmap-for-name-changes/
• https://github.com/pypa/pip/blob/main/.mailmap

[emmatyping]

It's somewhat possible by adding a .mailmap file to the repo

True, and I actually thought about this, but that also seems like a lot of noise to introduce a new file to the repo root, especially if it's just for me. I'd rather someone find my old email by accident than telegraph the change. The old email forwards and is still tied to my Github account 🤷‍♀️