It seems to me that major changes happen on release boundaries; in Matt's example, on the 3.00 boundary. Many compatibility changes happen for "pre-version X.XX" versus "version X.XX and later." If that's true, why not use < (less than) and >= (greater than or equal), since it seems that it would fit the convention that we use when deploying releases. It also avoids the problem of modifying earlier releases. For example, we could write a rule that uses " < 2.4.0 " and ">= 2.4.0", so that after 2.4.0 is released, we could release 2.2.19, 2.2.94733, etc, and we don't have to change the rule (of course, as long as the functionality of 2.2.X doesn't change). We also avoid the problem of either duplicating or not considering the "=" case. A random thought? -Jeff _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
