I've made some scripts which create a temporary copy of the dillo CVS dir and the patched dir, remove all unwanted crud from the patched dir, do the diff and generate some statistics. I can send them if you want.
Hm, a script, didn't thought about that. No need to send them though, can make my own if I need any.
Of course this still leaves the issues with patch makers constantly being out of sync with eachother, and each patch being broken by updates to CVS shortly after the patch was posted. More on that later...
What about making a seperate Dillo repository, but instead of using CVS that is too centralized and can't handle branches very well (or so I heard), we could use GNU Arch (http://www.gnu.org/software/gnu-arch/, thanks to Paul Pelzl for the tip) or Bitkeeper? That way it should be much easier to manage all the patches, with one branch for each "patch" (one branch for https, one for tab+frames, etc). The hardest part should be to keep our main branch in sync with Dillo's CVS. Greetings, Indan