The State of Go
Edit: This commit was written to the original submission: https://talks.golang.org/2015/state-of-go.slide#7--------------It seems like these people simply don't understand Github very well.    Can only view diffs on a single page (can be very slow).
    Cannot compare differences between patch sets.
    Accepting a patch creates a "merge commit" (ugly repo history).

Don't use the merge button, just add the requester's repo as a remote to yours and use your familiar tools. If possible and done, a fast-forward merge + push will also close the PR.    Comments are sent as they are written; you cannot "draft" comments.

How is that different from pull requests via emails? (Also, on the website itself the comments can be edited.)    To create a patch one must fork the repository publicly
    (weird and unnecessary).

What exactly is weird about that? It makes it possible for the requestor to craft their changes with full control, without requiring upstream to give them write access. This point is just entirely nonsensical.    In general, pull request culture is not about code review.

A strong claim, but one without any justification, and which is, in my experience, as far from the truth as possible.Edit:In light of their complaints about the need to fork, i have to say that their current contribution process can in its entirety be described as weird, unnecessary and baroque:https://golang.org/doc/contribute.html