Dave Thaler's approach to resolve a similar problem for tinycbor was to fork the github repo and apply all pull requests to the fork:
https://github.com/dthaler/tinycbor Can we do this same thing for mbedtls? It would be much easier to maintain if we didn't have a patch in the repo. But if we must have a patch in the repo, I recommend something like quilt: http://savannah.nongnu.org/projects/quilt Cheers, C.J. On Mon, Jun 12, 2017 at 9:51 PM, Thiago Macieira <thiago.macieira at intel.com> wrote: > On segunda-feira, 12 de junho de 2017 17:34:04 PDT Mats Wichmann wrote: > > as far as I can see, the push to mbedtls 2.4.2 broke the patch that is > > applied on top of that repository. I'm seeing 100% of the builders fail > > now, with these sorts of messages: > > Let's start by cleaning up that patch. > > Can we erase it and recreate in smaller chunks? Each file must have the > number > of the upstream pull request. I contacted Microsoft and obtained the > following > list for theirs: > > https://github.com/ARMmbed/mbedtls/pull/730 > https://github.com/ARMmbed/mbedtls/pull/731 > https://github.com/ARMmbed/mbedtls/pull/858 > > Can Samsung developers provide the link to theirs? > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170613/d74e7b65/attachment.html>
