:16 AM
To: Nithin Raju
Cc: Saurabh Shah; dev@openvswitch.org; Samuel Ghinet
Subject: Re: [ovs-dev] Recent series of patches
Yes, it would be helpful to use that form. So far I've transformed
the issue references in the patches I've committed into that form. If
some other form is better for
Yes, it would be helpful to use that form. So far I've transformed
the issue references in the patches I've committed into that form. If
some other form is better for github then let's write up the
appropriate format as a patch to CONTRIBUTING.
Thanks,
Ben.
On Wed, Aug 06, 2014 at 09:14:23PM +
BTW, CONTRIBUTING file mentions a "Reported-at: " that we could use to provide
specific links to the issue addressed.
-- Nithin
On Aug 6, 2014, at 2:01 PM, Saurabh Shah
wrote:
>> Since our issue tracker is in a different repo from the code, I think you
>> need
>> to reference issues in the f
> Since our issue tracker is in a different repo from the code, I think you need
> to reference issues in the following way:
>
> ovs/ovs-issues#42
>
This is good to know. I wasn't aware about this. Thanks Justin!
-- Saurabh
___
dev mailing
;>
Date: Wednesday, August 6, 2014 at 9:49 AM
To: Samuel Ghinet
mailto:sghi...@cloudbasesolutions.com>>
Cc: "dev@openvswitch.org<mailto:dev@openvswitch.org>"
mailto:dev@openvswitch.org>>
Subject: Re: [ovs-dev] Recent series of patches
Thanks, Samuel, for posting th
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 th
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
