Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Numan Siddique]

On Wed, May 8, 2019 at 1:03 AM Mark Michelson  wrote:

> On 5/7/19 1:42 PM, Numan Siddique wrote:
> >
> >
> > On Sat, Apr 27, 2019 at 5:51 AM Justin Pettit  > > wrote:
> >
> >
> >  > On Apr 26, 2019, at 2:50 PM, Mark Michelson  > > wrote:
> >  >
> >  > On 4/26/19 3:42 PM, Ben Pfaff wrote:
> >  >
> >  >> We need to pick a date (or a trigger) for freezing the OVN parts
> > of OVS.
> >  >> I don't know what that date should be.  Thoughts?
> >  >
> >  > I'm of the opinion that it should be ASAP. With the new repo
> > created, it's best for developers to start using the new repo for
> > their day-to-day development. Adding more commits to the OVS repo at
> > this point will potentially result in lost work if a maintainer
> > neglects to get it moved over.
> >
> > I think we should continue to do development in the OVS repo until
> > we're certain that the approach being taken is the right one and
> > that we've got all the pieces in place to fully do OVN development
> > on its own (e.g., separate mailing list, CI/CD infrastructure,
> > etc).  Once we have all those pieces in place, then we should delete
> > the "ovn" branch from the OVS repo.  Having the place where it has
> > traditionally lived continue on in a zombie state will be confusing,
> > and possibly problematic if we decide the path we're currently going
> > down is wrong for some reason.  Those concerns combined with your
> > imminent paternity lean me towards waiting.
> >
> > Let's see how things go for the next couple months, and then revisit
> > if it's time to stop development in the "ovn" branch.  If it goes as
> > I expect, I'll enthusiastically support that change.
> >
> >
> > Till we have every thing in place and remove "ovn" folder from the ovs
> > repo, the ovn-org/ovn repo would be out of sync w.r.t to OVN related
> > patches.
> > So is it fine if we apply the OVN related patches to the new repo once
> > the patch is merged in ovs repo ? If in case we agree to apply these
> > patches, will there be any mismatch in
> > the history ? (like commit id being different).
> > Or lets sync the ovn-org/ovn repo when we decide to make it official.
> >
> > Any thoughts ?
>
> What methods exist for syncing the commits in one go? And would such a
> method also preserve commit ids and other history? If it's not too hard
> to perform this, then it's probably the best way to go. I think doing
> everything in one big change is easier than trying to do a bunch of
> small changes as needed.
>

Agree. At this point I am not aware of any syncing methods. I will try to
explore.

Thanks
Numan


>
> >
> > Thanks
> > Numan
> >
> >
> >
> > Thanks,
> >
> > --Justin
> >
> >
>
>
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Mark Michelson]

On 5/7/19 1:42 PM, Numan Siddique wrote:



On Sat, Apr 27, 2019 at 5:51 AM Justin Pettit > wrote:



 > On Apr 26, 2019, at 2:50 PM, Mark Michelson mailto:mmich...@redhat.com>> wrote:
 >
 > On 4/26/19 3:42 PM, Ben Pfaff wrote:
 >
 >> We need to pick a date (or a trigger) for freezing the OVN parts
of OVS.
 >> I don't know what that date should be.  Thoughts?
 >
 > I'm of the opinion that it should be ASAP. With the new repo
created, it's best for developers to start using the new repo for
their day-to-day development. Adding more commits to the OVS repo at
this point will potentially result in lost work if a maintainer
neglects to get it moved over.

I think we should continue to do development in the OVS repo until
we're certain that the approach being taken is the right one and
that we've got all the pieces in place to fully do OVN development
on its own (e.g., separate mailing list, CI/CD infrastructure,
etc).  Once we have all those pieces in place, then we should delete
the "ovn" branch from the OVS repo.  Having the place where it has
traditionally lived continue on in a zombie state will be confusing,
and possibly problematic if we decide the path we're currently going
down is wrong for some reason.  Those concerns combined with your
imminent paternity lean me towards waiting.

Let's see how things go for the next couple months, and then revisit
if it's time to stop development in the "ovn" branch.  If it goes as
I expect, I'll enthusiastically support that change.


Till we have every thing in place and remove "ovn" folder from the ovs 
repo, the ovn-org/ovn repo would be out of sync w.r.t to OVN related 
patches.
So is it fine if we apply the OVN related patches to the new repo once 
the patch is merged in ovs repo ? If in case we agree to apply these 
patches, will there be any mismatch in

the history ? (like commit id being different).
Or lets sync the ovn-org/ovn repo when we decide to make it official.

Any thoughts ?


What methods exist for syncing the commits in one go? And would such a 
method also preserve commit ids and other history? If it's not too hard 
to perform this, then it's probably the best way to go. I think doing 
everything in one big change is easier than trying to do a bunch of 
small changes as needed.




Thanks
Numan



Thanks,

--Justin




___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Numan Siddique]

On Sat, Apr 27, 2019 at 5:51 AM Justin Pettit  wrote:

>
> > On Apr 26, 2019, at 2:50 PM, Mark Michelson  wrote:
> >
> > On 4/26/19 3:42 PM, Ben Pfaff wrote:
> >
> >> We need to pick a date (or a trigger) for freezing the OVN parts of OVS.
> >> I don't know what that date should be.  Thoughts?
> >
> > I'm of the opinion that it should be ASAP. With the new repo created,
> it's best for developers to start using the new repo for their day-to-day
> development. Adding more commits to the OVS repo at this point will
> potentially result in lost work if a maintainer neglects to get it moved
> over.
>
> I think we should continue to do development in the OVS repo until we're
> certain that the approach being taken is the right one and that we've got
> all the pieces in place to fully do OVN development on its own (e.g.,
> separate mailing list, CI/CD infrastructure, etc).  Once we have all those
> pieces in place, then we should delete the "ovn" branch from the OVS repo.
> Having the place where it has traditionally lived continue on in a zombie
> state will be confusing, and possibly problematic if we decide the path
> we're currently going down is wrong for some reason.  Those concerns
> combined with your imminent paternity lean me towards waiting.
>
> Let's see how things go for the next couple months, and then revisit if
> it's time to stop development in the "ovn" branch.  If it goes as I expect,
> I'll enthusiastically support that change.
>

Till we have every thing in place and remove "ovn" folder from the ovs
repo, the ovn-org/ovn repo would be out of sync w.r.t to OVN related
patches.
So is it fine if we apply the OVN related patches to the new repo once the
patch is merged in ovs repo ? If in case we agree to apply these patches,
will there be any mismatch in
the history ? (like commit id being different).
Or lets sync the ovn-org/ovn repo when we decide to make it official.

Any thoughts ?

Thanks
Numan




>
> Thanks,
>
> --Justin
>
>
>
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Justin Pettit]

> On Apr 26, 2019, at 2:50 PM, Mark Michelson  wrote:
> 
> On 4/26/19 3:42 PM, Ben Pfaff wrote:
> 
>> We need to pick a date (or a trigger) for freezing the OVN parts of OVS.
>> I don't know what that date should be.  Thoughts?
> 
> I'm of the opinion that it should be ASAP. With the new repo created, it's 
> best for developers to start using the new repo for their day-to-day 
> development. Adding more commits to the OVS repo at this point will 
> potentially result in lost work if a maintainer neglects to get it moved over.

I think we should continue to do development in the OVS repo until we're 
certain that the approach being taken is the right one and that we've got all 
the pieces in place to fully do OVN development on its own (e.g., separate 
mailing list, CI/CD infrastructure, etc).  Once we have all those pieces in 
place, then we should delete the "ovn" branch from the OVS repo.  Having the 
place where it has traditionally lived continue on in a zombie state will be 
confusing, and possibly problematic if we decide the path we're currently going 
down is wrong for some reason.  Those concerns combined with your imminent 
paternity lean me towards waiting.

Let's see how things go for the next couple months, and then revisit if it's 
time to stop development in the "ovn" branch.  If it goes as I expect, I'll 
enthusiastically support that change.

Thanks,

--Justin


___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Mark Michelson]

On 4/26/19 3:42 PM, Ben Pfaff wrote:

On Fri, Apr 26, 2019 at 11:14:23AM +0530, Numan Siddique wrote:

On Fri, Apr 26, 2019 at 1:56 AM Ben Pfaff  wrote:


On Thu, Apr 25, 2019 at 12:51:29PM -0700, Ben Pfaff wrote:

On Thu, Apr 25, 2019 at 08:38:06AM -0400, Mark Michelson wrote:

Yesterday, I once again performed the task of splitting OVN from OVS

(I've

gotten pretty good at it now). This time, rather than living in a

personal

repo, you can find the ovn repo at https://github.com/ovn-org/ovn.git


I noticed that most or all of your commits lack sign-offs.  Oops?


By the way, I guess that you should be the main person pushing to this
repo for now, so I'll review some patches but I'll plan to mostly ack
them rather than applying them to the new repo.




Thanks Mark for all the work.
Shall we consider that all the OVN patches will now be applied to the new
repo ?
If so, then all the present OVN patches under review should be resubmitted ?


We need to pick a date (or a trigger) for freezing the OVN parts of OVS.
I don't know what that date should be.  Thoughts?



I'm of the opinion that it should be ASAP. With the new repo created, 
it's best for developers to start using the new repo for their 
day-to-day development. Adding more commits to the OVS repo at this 
point will potentially result in lost work if a maintainer neglects to 
get it moved over.

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Ben Pfaff]

On Fri, Apr 26, 2019 at 11:14:23AM +0530, Numan Siddique wrote:
> On Fri, Apr 26, 2019 at 1:56 AM Ben Pfaff  wrote:
> 
> > On Thu, Apr 25, 2019 at 12:51:29PM -0700, Ben Pfaff wrote:
> > > On Thu, Apr 25, 2019 at 08:38:06AM -0400, Mark Michelson wrote:
> > > > Yesterday, I once again performed the task of splitting OVN from OVS
> > (I've
> > > > gotten pretty good at it now). This time, rather than living in a
> > personal
> > > > repo, you can find the ovn repo at https://github.com/ovn-org/ovn.git
> > >
> > > I noticed that most or all of your commits lack sign-offs.  Oops?
> >
> > By the way, I guess that you should be the main person pushing to this
> > repo for now, so I'll review some patches but I'll plan to mostly ack
> > them rather than applying them to the new repo.
> >
> 
> 
> Thanks Mark for all the work.
> Shall we consider that all the OVN patches will now be applied to the new
> repo ?
> If so, then all the present OVN patches under review should be resubmitted ?

We need to pick a date (or a trigger) for freezing the OVN parts of OVS.
I don't know what that date should be.  Thoughts?
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Mark Michelson]

On 4/26/19 1:47 AM, Numan Siddique wrote:



On Fri, Apr 26, 2019 at 11:14 AM Numan Siddique > wrote:




On Fri, Apr 26, 2019 at 1:56 AM Ben Pfaff mailto:b...@ovn.org>> wrote:

On Thu, Apr 25, 2019 at 12:51:29PM -0700, Ben Pfaff wrote:
 > On Thu, Apr 25, 2019 at 08:38:06AM -0400, Mark Michelson wrote:
 > > Yesterday, I once again performed the task of splitting OVN
from OVS (I've
 > > gotten pretty good at it now). This time, rather than
living in a personal
 > > repo, you can find the ovn repo at
https://github.com/ovn-org/ovn.git
 >
 > I noticed that most or all of your commits lack sign-offs.  Oops?

By the way, I guess that you should be the main person pushing
to this
repo for now, so I'll review some patches but I'll plan to
mostly ack
them rather than applying them to the new repo.



Thanks Mark for all the work.
Shall we consider that all the OVN patches will now be applied to
the new repo ?
If so, then all the present OVN patches under review should be
resubmitted ?

Thanks
Numan


I found an issue when compiling if I configure like below

$mkdir _gcc
$ cd _gcc
$.../configure --enable-Werror
$make -C _gcc -j5
...
libtool: link: gcc -Wstrict-prototypes -Wall -Wextra -Wno-sign-compare 
-Wpointer-arith -Wformat -Wformat-security -Wswitch-enum 
-Wunused-parameter -Wbad-function-cast -Wcast-align -Wstrict-prototypes 
-Wold-style-definition -Wmissing-prototypes -Wmissing-field-initializers 
-fno-strict-aliasing -Wswitch-bool -Wlogical-not-parentheses 
-Wsizeof-array-argument -Wbool-compare -Wshift-negative-value 
-Wduplicated-cond -Wshadow -Wmultistatement-macros -Wcast-align=strict 
-Werror -Werror -g -O2 -o vswitchd/ovs-vswitchd vswitchd/bridge.o 
vswitchd/ovs-vswitchd.o vswitchd/system-stats.o vswitchd/xenserver.o  
ofproto/.libs/libofproto.a 
/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc/ovs/lib/.libs/libsflow.a 
lib/.libs/libsflow.a lib/.libs/libopenvswitch.a -lssl -lcrypto -lcap-ng 
-latomic -lpthread -lrt -lm -lunbound

touch -c manpage-check
make[4]: Leaving directory 
'/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc/ovs'
make[3]: Leaving directory 
'/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc/ovs'
make[2]: Leaving directory 
'/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc/ovs'

make[2]: Entering directory '/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc'
make[2]: *** No rule to make target '../ovs/ovsdb/libovsdb.la 
', needed by 'utilities/ovn-nbctl'.  Stop.

make[2]: *** Waiting for unfinished jobs
make[2]: Leaving directory '/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc'
make[1]: *** [Makefile:3346: all-recursive] Error 1
make[1]: Leaving directory '/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc'
make: *** [Makefile:2216: all] Error 2
make: Leaving directory '/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc'
...

We need to fix this.

Thanks
Numan


I tried this and actually got a slightly different build error:

/bin/sh ./libtool  --tag=CC   --mode=link gcc -Wstrict-prototypes -Wall 
-Wextra -Wno-sign-compare -Wpointer-arith -Wformat -Wformat-security 
-Wswitch-enum -Wunused-parameter -Wbad-function-cast -Wcast-align 
-Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes 
-Wmissing-field-initializers -fno-strict-aliasing -Wswitch-bool 
-Wlogical-not-parentheses -Wsizeof-array-argument -Wbool-compare 
-Wshift-negative-value -Wduplicated-cond -Wshadow-g -O2 -o 
utilities/ovn-nbctl utilities/ovn-nbctl.o lib/libovn.la 
../ovs/ovsdb/libovsdb.la ../ovs/lib/libopenvswitch.la -lpthread -lrt -lm 
 -lunbound
libtool:   error: cannot find the library '../ovs/ovsdb/libovsdb.la' or 
unhandled argument '../ovs/ovsdb/libovsdb.la'


In both cases though, it appears the issue is that it is trying to 
either build or find ovs libraries from the top-level source directory, 
but they have been built in the _gcc subdirectory. I'm looking into this 
to try to fix it.

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Mark Michelson]

On 4/26/19 1:44 AM, Numan Siddique wrote:



On Fri, Apr 26, 2019 at 1:56 AM Ben Pfaff > wrote:


On Thu, Apr 25, 2019 at 12:51:29PM -0700, Ben Pfaff wrote:
 > On Thu, Apr 25, 2019 at 08:38:06AM -0400, Mark Michelson wrote:
 > > Yesterday, I once again performed the task of splitting OVN
from OVS (I've
 > > gotten pretty good at it now). This time, rather than living in
a personal
 > > repo, you can find the ovn repo at
https://github.com/ovn-org/ovn.git
 >
 > I noticed that most or all of your commits lack sign-offs.  Oops?

By the way, I guess that you should be the main person pushing to this
repo for now, so I'll review some patches but I'll plan to mostly ack
them rather than applying them to the new repo.



Thanks Mark for all the work.
Shall we consider that all the OVN patches will now be applied to the 
new repo ?


OVN is buildable and testable in the new repo, so developers should be 
able to do their work against the new repo.



If so, then all the present OVN patches under review should be resubmitted ?


Yes, unfortunately. The structure of the new repo should allow for 
patches to be applied fairly easily, as long as the patches are only for 
ovn. The ovn/ subdirectory has been promoted to the top level. So it 
should be possible to apply a patch using `git apply -p2 ` or 
`patch -p2 < `


If your patch touches both OVS and OVN, then the patch will need to be 
split so that the OVS parts are submitted to OVS and the OVN parts are 
submitted to OVN. Note that a policy for doing this sort of development 
is in the TODO_SPLIT.rst file.




Thanks
Numan

___
dev mailing list
d...@openvswitch.org 
https://mail.openvswitch.org/mailman/listinfo/ovs-dev



___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Mark Michelson]

On 4/25/19 3:51 PM, Ben Pfaff wrote:

On Thu, Apr 25, 2019 at 08:38:06AM -0400, Mark Michelson wrote:

Yesterday, I once again performed the task of splitting OVN from OVS (I've
gotten pretty good at it now). This time, rather than living in a personal
repo, you can find the ovn repo at https://github.com/ovn-org/ovn.git


I noticed that most or all of your commits lack sign-offs.  Oops?



Oops indeed. I tend to add the sign-off when using `git format-patch` 
when I send an e-mail. In this case since I pushed the commits directly, 
I skipped over that step.

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Numan Siddique]

On Fri, Apr 26, 2019 at 11:14 AM Numan Siddique  wrote:

>
>
> On Fri, Apr 26, 2019 at 1:56 AM Ben Pfaff  wrote:
>
>> On Thu, Apr 25, 2019 at 12:51:29PM -0700, Ben Pfaff wrote:
>> > On Thu, Apr 25, 2019 at 08:38:06AM -0400, Mark Michelson wrote:
>> > > Yesterday, I once again performed the task of splitting OVN from OVS
>> (I've
>> > > gotten pretty good at it now). This time, rather than living in a
>> personal
>> > > repo, you can find the ovn repo at https://github.com/ovn-org/ovn.git
>> >
>> > I noticed that most or all of your commits lack sign-offs.  Oops?
>>
>> By the way, I guess that you should be the main person pushing to this
>> repo for now, so I'll review some patches but I'll plan to mostly ack
>> them rather than applying them to the new repo.
>>
>
>
> Thanks Mark for all the work.
> Shall we consider that all the OVN patches will now be applied to the new
> repo ?
> If so, then all the present OVN patches under review should be resubmitted
> ?
>
> Thanks
> Numan
>
>
I found an issue when compiling if I configure like below

$mkdir _gcc
$ cd _gcc
$.../configure --enable-Werror
$make -C _gcc -j5
...
libtool: link: gcc -Wstrict-prototypes -Wall -Wextra -Wno-sign-compare
-Wpointer-arith -Wformat -Wformat-security -Wswitch-enum -Wunused-parameter
-Wbad-function-cast -Wcast-align -Wstrict-prototypes -Wold-style-definition
-Wmissing-prototypes -Wmissing-field-initializers -fno-strict-aliasing
-Wswitch-bool -Wlogical-not-parentheses -Wsizeof-array-argument
-Wbool-compare -Wshift-negative-value -Wduplicated-cond -Wshadow
-Wmultistatement-macros -Wcast-align=strict -Werror -Werror -g -O2 -o
vswitchd/ovs-vswitchd vswitchd/bridge.o vswitchd/ovs-vswitchd.o
vswitchd/system-stats.o vswitchd/xenserver.o  ofproto/.libs/libofproto.a
/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc/ovs/lib/.libs/libsflow.a
lib/.libs/libsflow.a lib/.libs/libopenvswitch.a -lssl -lcrypto -lcap-ng
-latomic -lpthread -lrt -lm -lunbound
touch -c manpage-check
make[4]: Leaving directory
'/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc/ovs'
make[3]: Leaving directory
'/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc/ovs'
make[2]: Leaving directory
'/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc/ovs'
make[2]: Entering directory '/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc'
make[2]: *** No rule to make target '../ovs/ovsdb/libovsdb.la', needed by
'utilities/ovn-nbctl'.  Stop.
make[2]: *** Waiting for unfinished jobs
make[2]: Leaving directory '/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc'
make[1]: *** [Makefile:3346: all-recursive] Error 1
make[1]: Leaving directory '/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc'
make: *** [Makefile:2216: all] Error 2
make: Leaving directory '/home/nusiddiq/workspace_cpp/ovn-org/ovn/_gcc'
...

We need to fix this.

Thanks
Numan


>
>
>> ___
>> dev mailing list
>> d...@openvswitch.org
>> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>>
>
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Numan Siddique]

On Fri, Apr 26, 2019 at 1:56 AM Ben Pfaff  wrote:

> On Thu, Apr 25, 2019 at 12:51:29PM -0700, Ben Pfaff wrote:
> > On Thu, Apr 25, 2019 at 08:38:06AM -0400, Mark Michelson wrote:
> > > Yesterday, I once again performed the task of splitting OVN from OVS
> (I've
> > > gotten pretty good at it now). This time, rather than living in a
> personal
> > > repo, you can find the ovn repo at https://github.com/ovn-org/ovn.git
> >
> > I noticed that most or all of your commits lack sign-offs.  Oops?
>
> By the way, I guess that you should be the main person pushing to this
> repo for now, so I'll review some patches but I'll plan to mostly ack
> them rather than applying them to the new repo.
>


Thanks Mark for all the work.
Shall we consider that all the OVN patches will now be applied to the new
repo ?
If so, then all the present OVN patches under review should be resubmitted ?

Thanks
Numan



> ___
> dev mailing list
> d...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Ben Pfaff]

On Thu, Apr 25, 2019 at 12:51:29PM -0700, Ben Pfaff wrote:
> On Thu, Apr 25, 2019 at 08:38:06AM -0400, Mark Michelson wrote:
> > Yesterday, I once again performed the task of splitting OVN from OVS (I've
> > gotten pretty good at it now). This time, rather than living in a personal
> > repo, you can find the ovn repo at https://github.com/ovn-org/ovn.git
> 
> I noticed that most or all of your commits lack sign-offs.  Oops?

By the way, I guess that you should be the main person pushing to this
repo for now, so I'll review some patches but I'll plan to mostly ack
them rather than applying them to the new repo.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS/OVN Split initial commits are complete

[Ben Pfaff]

On Thu, Apr 25, 2019 at 08:38:06AM -0400, Mark Michelson wrote:
> Yesterday, I once again performed the task of splitting OVN from OVS (I've
> gotten pretty good at it now). This time, rather than living in a personal
> repo, you can find the ovn repo at https://github.com/ovn-org/ovn.git

I noticed that most or all of your commits lack sign-offs.  Oops?
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev