[ovs-dev] [PATCH ovn-org/ovn 1/1] tests: Remove non OVN test files
Aaron Conole
aconole at redhat.com
Thu May 9 13:01:45 UTC 2019
Numan Siddique <nusiddiq at redhat.com> writes:
> On Thu, May 9, 2019 at 8:14 AM Mark Michelson <mmichels at redhat.com> wrote:
>
> On Wed, May 8, 2019, 20:35 Ben Pfaff <blp at ovn.org> wrote:
>
> On Wed, May 08, 2019 at 04:15:59PM -0400, Aaron Conole wrote:
> > Hi Numan,
> >
> > (also, CC'ing Mark)
> >
> > 0-day Robot <robot at bytheb.org> writes:
> >
> > > Bleep bloop. Greetings Numan Siddique, I am a robot and I have tried out your patch.
> > > Thanks for your contribution.
> > >
> > > I encountered some error that I wasn't expecting. See the details below.
> >
> > I think it makes sense to use the 'ovn-org/ovn' bracketed string as a
> > way of sending the patch to the OVN github repo for processing. I'm
> > glad you proposed something with this patch.
> >
> > Is there any objection to settling on that? Then I can make the bot "do
> > the right thing" :-)
>
> To me it seems longer than necessary, I'd think "ovn" by itself would be
> enough.
>
> I agree with Ben. The longer the required patch prefix, the less information can be conveyed in
> the first line of the commit message
>
> Ok. Sounds good to me.
>
> I will submit the patch with the prefix - "[PATCH][ovn] ...."
You can even shorten it:
[PATCH ovn] ...
should also work :)
It can be made to appear like that with the --subject-prefix argument to
git-format-patch:
$ git format-patch HEAD~ --subject-prefix="PATCH ovn"
> Thanks
> Numan
More information about the dev
mailing list