I'm not a huge fan of changing userspace visible API... Deleting this doesn't seem to gain much. If anything I'd add this into the CT code as just one more thing it registers. That said, I don't really have a vote here, and don't really want to do the work... And cleanup is really good... OTOH, this cleanup doesn't really help much - it is pretty much entirely self contained. (I don't see a clean way to do maintain backward compatibility in the userspace tool... it's easy enough to convert to CT on load, but how do you know what to print it out as afterwards? Do you just print as the new format?) On Mon, Sep 3, 2012 at 1:33 AM, Oliver <olipro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > On Monday 03 September 2012 15:57:53 you wrote: >> So no objections from you, right? :) > > Meanwhile, -m state lives on. > > In all honesty, if you're going to obliterate things like this, it's arguably > only fair to also implement something in your userland tools to catch the > change, throw a deprecated warning and appropriately modify it to use CT > instead. > > I would argue the same for those who wish to see the death of -m state (myself > included) > > Regards, > Oliver > -- > To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
