But your point about announcing changes on this list has changed my mind.
Richard Gooch wrote:
> No, the best way to announce a change is to tell people in words on
> the kernel list.
I doubt if all the driver writers read the list.
Especially authors of the really old drivers.
On the other hand, I expect they do check a kernel every now and then to
see if anything's changed in _their_ code.
I'm extrapolating from my own experience here. I do not always have
time to monitor the kernel list. And catching up on 6 months of
archives is impractical. But I have looked at old and new versions of
source I contributed (even though it's only small), and seen changes
that I might have something to say about that way.
> It should not be necessary to read the patches to see what's changed.
Perhaps, but reading the patches is much less time consuming than
reading the kernel list. And you can diff between any two kernel
versions to see if your code has been stomped on in the meantime.
You _don't_ have to read all the the patches to see changes to your own
contributed drivers. Just apply patches and compare relevant source.
You _do_ have to read all the kernel list to catch announcements.
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html