On Mon, 11 Jul 2016 11:49:16 +0900 Shinpei Muraoka <[email protected]> wrote:
> Hi Fujita-San > >> We should have really good reason to break the API compatibility with >> the older versions. I don't think that this is the case. >> >> Seems that better to revert this. Can we cleanly revert this? Any >> other side effect? > > I think it have side effect and it need some patches. > > If "[PATCH v2 0/8] Support some NXAction" looks patch good, > I will make patch for "[PATCH 4/7] ofproto/nx_actions: Update > arguments to be compatible with ovs-ofctl" > based on this patch. > > If "[PATCH v2 0/8] Support some NXAction" is difficult to marge, > Please discard this patch. > I will make patch based on current master. You mean that after I apply [PATCH v2 0/8] Support some NXAction then you send a patch to revert commit 3c3896fd77f274ce953dcb78795aa5cc4fde6c65 Author: Shinpei Muraoka <[email protected]> Date: Mon Jun 6 09:48:12 2016 +0900 ofproto/nx_actions: Update arguments to be compatible with ovs-ofctl Do I correctly understand what you mean? I'm also concerned about the subject of the following patch in the new patchset: [PATCH v2 3/8] ofproto/nx_actions: Update arguments to be compatible with ovs-ofctl You try to add start/end as optional arguments and converts to ofs/nbits to keep the compatibility? Or revert the whole start/end stuff? ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
