On 4/26/19 1:44 AM, Numan Siddique wrote:
On Fri, Apr 26, 2019 at 1:56 AM Ben Pfaff <b...@ovn.org
<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 ?
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 <patch>` or
`patch -p2 < <patch>`
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 <mailto: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
