Re: [ovs-dev] monitor2--delay past branch for 2.5?

2015-12-01 Thread Ben Pfaff
On Tue, Dec 01, 2015 at 02:23:40AM -0800, Andy Zhou wrote: > On Mon, Nov 30, 2015 at 9:58 AM, Ben Pfaff wrote: > > > Hi Andy. I think that we're planning to branch for 2.5 pretty soon. At > > the same time, I think that the monitor2 code is close to being ready. > > However, since we want to ad

Re: [ovs-dev] monitor2--delay past branch for 2.5?

2015-12-01 Thread Andy Zhou
On Mon, Nov 30, 2015 at 11:31 PM, Liran Schour wrote: > "dev" wrote on 30/11/2015 07:58:28 PM: > > > > > Hi Andy. I think that we're planning to branch for 2.5 pretty soon. At > > the same time, I think that the monitor2 code is close to being ready. > > However, since we want to add more func

Re: [ovs-dev] monitor2--delay past branch for 2.5?

2015-12-01 Thread Andy Zhou
On Mon, Nov 30, 2015 at 9:58 AM, Ben Pfaff wrote: > Hi Andy. I think that we're planning to branch for 2.5 pretty soon. At > the same time, I think that the monitor2 code is close to being ready. > However, since we want to add more functionality to monitor2 (conditions > for rows), it seems to

Re: [ovs-dev] monitor2--delay past branch for 2.5?

2015-11-30 Thread Liran Schour
"dev" wrote on 30/11/2015 07:58:28 PM: > > Hi Andy. I think that we're planning to branch for 2.5 pretty soon. At > the same time, I think that the monitor2 code is close to being ready. > However, since we want to add more functionality to monitor2 (conditions > for rows), it seems to me that

[ovs-dev] monitor2--delay past branch for 2.5?

2015-11-30 Thread Ben Pfaff
Hi Andy. I think that we're planning to branch for 2.5 pretty soon. At the same time, I think that the monitor2 code is close to being ready. However, since we want to add more functionality to monitor2 (conditions for rows), it seems to me that we should wait until after we branch 2.5 to commit