> The impact could be shown in a single email with a diffstat, for example. True, and I agree, but not the way stuff is usually done on LKML, thus probably not

> The impact could be shown in a single email with a diffstat, for example. True, and I agree, but not the way stuff is usually done on LKML, thus probably not considered. In this special case of a huge number of patches it might have been a good idea to present an RFC diffstat first, yes. Actually, I wish github had a .diffstat extension for pull requests, because often that's the first thing I care about before I know if I want to delve into a random big patch.