Is there a reason not to put this new machinery directly into encoding.h? The new machinery seems to be sufficient to implement the existing ::encode and ::decode types and should be compatible, right? With the containers, we can use template trickery to also forward the new functions when present in the mapped types. That would let us gradually adapt the code base. -Sam -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
