> real explanation, proper email addresses, proper shortlog, and proper diffstat.
> no sane word-wrap of the long description you type: github commit messages tend to be (if they have any description at all) one long unreadable line.
I don't know if github supports editing like that but by default it does one long line.
Related pain point: when I want to type out something in a fenced code block, it's a pain to have to switch back and forth. I do wish the editor forced a monospace font.
> Github explicit decided to eschew valid email addresses
No, that's a choice individual users make. As you can see from that help article, they have to explicitly set their git client to use an invalid email address if they want that. GitHub cannot and does not alter the email addresses contained in pushed commits. (Doing so would change the commit hash, making it an entirely different commit.)
> He explains in a later comment
Seems like the only thing missing is a way to wrap commit messages to 80 chars. Everything else is the fault of the person sending the PR, not GitHub. Also it only applies to commits _created_ from the GitHub Web UI. I don't know about you, but I only do that for extremely trivial changes.
> github throws away all the relevant information, like having even a valid email address for the person asking me to pull.
Github explicit decided to eschew valid email addresses: https://help.github.com/articles/keeping-your-email-address-...
He explains in a later comment: https://github.com/torvalds/linux/pull/17#issuecomment-56599...
> real explanation, proper email addresses, proper shortlog, and proper diffstat.
> no sane word-wrap of the long description you type: github commit messages tend to be (if they have any description at all) one long unreadable line.
I don't know if github supports editing like that but by default it does one long line.
Related pain point: when I want to type out something in a fenced code block, it's a pain to have to switch back and forth. I do wish the editor forced a monospace font.