> What is even harder to find out given a binary kernel is which patches (if
> any) have been applied to it. What if there was one file (say,
> /usr/src/linux/patches) to which each (well-behaved) patch would append a
> line or two (patch name, version, author, url), and then you could later
> extract that information the same way you extract .config?
I second that. It would be great to have a way of knowing what's different
from vanillia kernel. though:
* we can't expect each patch to do the 'magic thing'. But at least, those
big patches lying around could follow this kind of rule. I don't care about
typos patches, but It would be great to know that (for ex.) the rmap patch is
there or not.
* having /usr/src/linux/patches is not practical : it will be a big mess wrt
to conflict
The reason why I have not proposed something already is that I have no clue
how to achieve this purpose. But I still would like to have a way to know
which big patches have been in my kernel.
sorry,
Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Feb 07 2002 - 21:00:51 EST