On Thu, Feb 14, 2013 at 02:05:50PM +0000, Joe Thornber wrote: > When we've discussed this sort of thing before we've always decided > not to version sub modules and instead just rely on the overall kernel > version. Who are you intending should consume this DMINFO? People who have reason to look at their system logs when something they can't explain has happened (and then us, when they send snippets of the logs). All the optional dm sub-modules that plug into other modules report when they are loaded/unloaded. Then given that they are writing a line to the log, they might as well supply a version number in it, particularly if we're anticipating that once the core has settled down, future change will be concentrated around tuning these modules so we can't necessarily deduce which version of sub-module code is running from the module code version. Relying on the core kernel version just turns this into a lookup table maintenance problem to find out what patch was applied to what distro when. dm versioning gives us a quick distro-independent way to guess which version of our code was likely to have been running from information often included in the intial report of the problem. Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
