[ovs-dev] Recent series of patches

Justin Pettit jpettit at nicira.com
Wed Aug 6 16:49:59 UTC 2014

Thanks, Samuel, for posting those patches.  As Eitan mentioned, it's helpful to reference the issue number for tracking purposes.  It looks like Github is pretty smart about updating the issue tracker, too, when a commit goes in.

Since our issue tracker is in a different repo from the code, I think you need to reference issues in the following way:


Obviously, that would link the patch with issue number 42.


On August 6, 2014 at 9:36:41 AM, Eitan Eliahu (eliahue at vmware.com) wrote:
> Hi Sam,
> I was wondering if you could add an explanation for how (or if) each patch is related to  
> the open issues or enhancements that we filed in Github.
> I think we need to see a motivation which is aligned with the priority we assigned to the  
> open issues we filed. Otherwise, it would be hard to review or to understand the correct  
> context. I am not saying that each patch must to be correlated to a Github issue but we would  
> like to understand the context or the problem it solves.
> Thank you!
> Eitan
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev

More information about the dev mailing list