Many thanks for the details - and the reminder on passively contributing to wasting developers' time :-) For the content I created, I will proceed accordingly.
I've reached out to the repo owner where I got the patches I use to validate the MinGW build to see his opinion. If there is no conflict, I'll be pleased to follow the details you provided to submit the patches I use. I believe, George will provide his patch accordingly. Cheers, On Mon, 2 Oct 2017 at 16:47 Emil Velikov <emil.l.veli...@gmail.com> wrote: > On 2 October 2017 at 15:16, Trevor (CIMdata) <trevor.sa...@gmail.com> > wrote: > > Hello Emil, > > > > Yes, I did see the AppVeyor integraton for MSVC. It could be quite easy > to > > add the MinGW scope to the metrix. > > > > > > > > I don’t really know how to ‘upsteam’ the patches I use mostly because I > am > > not the author. Do I just submit a PR? Anyway to help George with his > patch > > – which fixes the MinGW build – I have done the CI script, AppVeyor.yml > and > > set up AV repo. My source if free and w/o license. Please feel free to > use > > it if you wish. Many thanks! > > > The top page while searching for "mesa submitting patches" gives [1]. > > Please skim through it but in a gist: > - fire git format-patch(ed) patches to the list. Since I'm lazy I > directly use git send-email $old_sha..$new_sha > - patches should have commit messages > - try to attribute the author when that's not you - see git commit > --author="foo" > > Keep in mind that if a developer has to spend time X applying OOT > patches, that's X less time for addressing other issues. > > Thanks > Emil > > [1] https://www.mesa3d.org/submittingpatches.html >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
