Frode Nordahl <frode.nord...@canonical.com> writes: > On Fri, Nov 22, 2019 at 11:46 AM Frode Nordahl > <frode.nord...@canonical.com> wrote: >> >> On Fri, Nov 22, 2019 at 11:12 AM Frode Nordahl >> <frode.nord...@canonical.com> wrote: >> > >> > This is weird, the patches apply on an up-to-date ovn repo with git am >> > on blobs from the list. >> > >> > I noticed the mailing list thread order is in reverse with patch >> > number two preceding patch number one, could that be the issue? >> >> It may also be me editing the output from ``git format-patch`` prior to >> submitting, but cannot reproduce the error reported by the bot locally >> with blobs gleaned from list, so would love to hear your views on >> what's going on here. > > Ah yes that must be it, the commit msg is part of the commit sha1 > and apparently I have tampered with it, so this is my bad. > > Sorry about the noise, I'll submit an untampered v2.
Glad it worked out :) In the future, you can try and grab the patch from the patchwork instance (https://patchwork.ozlabs.org/project/openvswitch/) and check that it matches and applies. I'll try to improve the output of the bot as well to include base commit information (so at least we can try to reproduce the errors). _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
