I don't think that is a clear description by any measure. It could be summarized in a couple of paragraphs. It's perhaps good for beginner programmers to learn from, so I'd encourage him to write a blog post. Pull request motivations should be to the point, especially for small changes, because otherwise they just waste time.
Meh, to each their own I guess. While it is long, that does not in any way make it unclear. In fact, he explicitly states the motivations and repercussions of each decision. To persuade the master developers, who made the "mistakes" (for lack of a better word) in the first place, this seems like a worthwhile pursuit.
The only thing that would have made this more entertaining would be if he had submitted a similar pull request to Linus..
