patch will work against the cvs from 11-11, but not from 11-10 (thats month-day) and the tabs patch will work against 11-10 and not 11-11.
Kind of a quandary, eh....
The joy of making patches against the CVS version... If the code would be in CVS, then it would stay automatically up to date. Normally, all patches should be made against some logical cvs tag, say, a release, but if the patches are still in development it's logical the maker want them to work with the current cvs version. Personally I'm going a bit crazy because of all those Dillo versions on my hd, one original cvs version, one I work on, one clean one to test if the patches really work, then two fake Dillo directories with symlinks to all the original files, so that I can do "diff -pur" and keep unwanted noise out of the patch, keeping it small and simple. Then I moved all those directories to another pc because I wanted to upgrade my 233 Mhz pc, someone gave me a pentum 3 800 + mobo, one of them more or less broken, whole pc very unstable. Caused major filesystem corruption when I tried it out, got it stable with underclocking the cpu to 700 Mhz, but still can't compile because I suddenly miss some header files. No big deal, I backuped everything, and wanted to switch to Slackware anyway, but still means I have to do all the Dillo stuff via ssh on the other pc, until I have everything back on track again. Anyway, the point was, Frank, you got some tips how to handle all those patches? My current system works fine, but I need yet another directory with Dillo source if I want to make or use another patch. Greetings, Indan