I guess George means, why is the file _both_ in the patch and in 2.1.72?
When patching from 2.1.72 to 2.1.73, I get:
The next patch would create the file `linux/include/linux/dmascc.h',
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to linux/include/linux/dmascc.h.rej
So, I editted the reject file to remove the patch stuff (s/^..//) and
then:
$ diff -u dmascc.h dmascc.h.new
$
No difference between the 2.1.72 version and the version included in
the 2.1.73 patch.
Hmm, apparently nobody uses the patches anymore but just downloads
complete kernels. Strange.
Mike.
-- Miquel van Smoorenburg | Studying to be a technomage <*> miquels@cistron.nl | "May you live in interesting times"